topic: tools
31 modules sharing the tools name family (derived from the tree's prefix discipline).
The 'tools' topic family in the Nishi sovereign ecosystem provides a framework for agent-facing tool execution and management, enabling modular, secure, and isolated tool interactions. The nx_tools_api exposes the tool registry over HTTP, while nx_tools_api_exec_gate enables real execution of tool calls through a gated interface. nx_tools_timing_exec_diagnostic offers read-only diagnostics for specific tool binaries, supporting reliability and performance analysis without altering system state.
auto-narrated by the local model from this topic's module headers; links verified against the wiki index.
narrated overview -- maintained by the narration lane, module links verified against this wiki.
| module | description | lines | funcs |
|---|---|---|---|
| nx_tools_api.nx | Exposes the nx_tool_registry over HTTP with GET and MCP-compatible JSON-RPC endpoints for tool discovery and invocation. | 2656 | 110 |
| nx_tools_api_candidate_t182.nx | Exposes the nx_tool_registry over HTTP with GET and MCP-compatible POST endpoints for tool discovery and invocation. | 2431 | 103 |
| nx_tools_api_canonical_candidate_t182.nx | 2430 | 103 | |
| nx_tools_api_exec_gate.nx | GATE for R2: the /mcp tools/call STUB is now REAL execution. Drives the live | 283 | 10 |
| nx_tools_api_gate.nx | drives ta_handle_pfx IN-PROCESS (no socket, no curl): register two test tools, then | 350 | 6 |
| nx_tools_api_idem_candidate_t190.nx | Exposes the nx_tool_registry over HTTP with MCP compatibility and idempotency for tool calls. | 2436 | 103 |
| nx_tools_api_recovery_candidate_t316.nx | Exposes the nx_tool_registry over HTTP with GET and MCP-compatible JSON-RPC endpoints for tool discovery and invocation. | 2648 | 110 |
| nx_tools_api_recovery_candidate_v2_t316.nx | Exposes the nx_tool_registry over HTTP with GET and MCP-compatible JSON-RPC endpoints for tool discovery and invocation. | 2654 | 110 |
| nx_tools_api_recovery_candidate_v3_t316.nx | Exposes the nx_tool_registry over HTTP with GET and MCP-compatible JSON-RPC endpoints for tool discovery and invocation. | 2656 | 110 |
| nx_tools_api_recovery_comparison_gate_t316.nx | 60 | 4 | |
| nx_tools_api_recovery_comparison_gate_v2_t316.nx | 60 | 4 | |
| nx_tools_api_recovery_comparison_gate_v3_t316.nx | 60 | 4 | |
| nx_tools_api_recovery_gate_t316.nx | 35 | 3 | |
| nx_tools_api_recovery_handler_gate_v3_t316.nx | 45 | 3 | |
| nx_tools_api_regression_complete_gate_v3_t316.nx | drives ta_handle_pfx IN-PROCESS (no socket, no curl): register two test tools, then | 353 | 6 |
| nx_tools_api_regression_gate_t316.nx | drives ta_handle_pfx IN-PROCESS (no socket, no curl): register two test tools, then | 350 | 6 |
| nx_tools_api_regression_gate_v2_t316.nx | drives ta_handle_pfx IN-PROCESS (no socket, no curl): register two test tools, then | 350 | 6 |
| nx_tools_api_regression_gate_v3_t316.nx | drives ta_handle_pfx IN-PROCESS (no socket, no curl): register two test tools, then | 350 | 6 |
| nx_tools_api_regression_isolated_gate_v3_t316.nx | drives ta_handle_pfx IN-PROCESS (no socket, no curl): register two test tools, then | 353 | 6 |
| nx_tools_api_serve.nx | standalone loopback HTTP server for the R0 agent-facing API (nx_tools_api). | 347 | 10 |
| nx_tools_argv_idem_gate.nx | Actual ta_mcp_call integration in a newly created private /tmp directory. | 101 | 5 |
| nx_tools_argv_unicode_gate.nx | 224 | 4 | |
| nx_tools_canary_gate.nx | CANARY for the tools daemon (debt seq1373). license_tier: ORIGINAL | 134 | 6 |
| nx_tools_denial_observation_candidate_t316.nx | Isolated candidate: merge functions into nx_tools_api after review; no production journal used by gate. | 16 | 2 |
| nx_tools_denial_observation_gate_t316.nx | 38 | 2 | |
| nx_tools_guidance_gate_t140.nx | Exercises canonical denial routing without minting credentials or editing the registry/allowlist. | 26 | 2 |
| nx_tools_listener_child_gate.nx | Actual source-linked child helper, fresh loopback listener and private cwd only. | 182 | 7 |
| nx_tools_timing_exec_diagnostic.nx | Read-only diagnostic of one explicitly supplied fixture ELF. No config or journal writes. | 33 | 1 |
| nx_tools_timing_fixture.nx | Dedicated fixture: stdout and exit only. All timings supplied by the gate. | 22 | 1 |
| nx_tools_timing_gate.nx | Real monotonic clock + existing journal writer, with an isolated caller-owned fixture. | 73 | 3 |
| nx_tools_timing_serve_gate.nx | Source-linked staged serve_one integration. No daemon startup/seed. Private pinned fixture only. | 261 | 7 |