Local MCP gateway — configure your MCP servers once and connect every MCP client (Claude, Codex, OpenCode) to one place.
Toolbx exposes 11 tools with mixed quality. Most tools have descriptions (9/11), but parameter documentation is sparse and inconsistent. Tool names follow verb_noun convention (tool import, tool list, tools search), which is good. However, schemas are incomplete: many parameters lack type information or descriptions. The 'greet' tool is a test fixture and should not be exposed. Error handling guidance is absent. Output schemas are not documented. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels (DESTRUCTIVE for tool remove, WRITE for tool enable/disable). Parameter descriptions are often generic ('override the resolved config path') without explaining constraints or expected formats.
Greets the named person.
Disable an imported custom tool.
Enable an imported custom tool.
Import a local .ts or .js custom tool file into Toolbx.
Show a custom tool manifest plus a head of its source file.
List imported custom tools.
Remove an imported custom tool (deletes its source file and manifest entry).
Disable an upstream tool from being exposed through Toolbx.
Enable an upstream tool exposed through Toolbx.
Destructive tool (tool remove) lacks confirmation pattern and error recovery guidance. No dry-run or confirmation step before deleting source files and manifest entries.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels declared in metadata. LLMs cannot infer which tools are safe to retry or have side effects.
Parameter descriptions are generic and lack constraints. 'config' parameter appears in 10 tools with identical description ('override the resolved config path') but no guidance on format, precedence, or validation rules.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | <=2025-11-25 | v2 |
List tools known to Toolbx.
Search tools known to Toolbx using the bootstrap-tool ranking.
Output schemas not documented. Tools like 'tools list' and 'tools search' return structured data (JSON or table) but LLMs have no schema to understand response fields, forcing parsing guesswork.
Test fixture 'greet' tool exposed in production tool list. This is a test artifact and should not be registered as a real tool.