Loading ToolBench
MCP server for intelligent file routing and content synchronization with metadata extraction and destination rule-based file organization
Critical failures across all dimensions. The single tool 'execute_skill_action' has a vague, generic name that violates verb_noun conventions. Description is 97 chars but lacks WHAT/WHEN/WHY context required by pattern:tool-description. Input schema shows object and array types but NO parameter descriptions whatsoever, violates pattern:tool-description requirement that every parameter needs a description. No output schema documented. No error handling guidance. The implementation in mcp_server.py is a stub that prints JSON and exits; it does not actually implement MCP protocol handshake, tool invocation, or request/response handling. This is not a functional MCP server.
Execute intelligent file routing and content synchronization skill action
Tool name 'execute_skill_action' is generic and violates verb_noun convention. 'execute' and 'action' are vague, LLMs cannot infer intent. Should be 'route_file' or 'sync_file_to_destination' to match actual behavior.
Input parameters 'file_metadata' and 'destination_rules' have NO descriptions. LLMs cannot determine what fields file_metadata should contain or what structure destination_rules expects. Violates pattern:tool-description requirement that every parameter needs a description.
No output schema documented. The example_usage.py shows a response with 'routed_destination', 'extracted_tags', 'sync_status' fields, but this is not formally declared in the tool definition. LLMs cannot plan downstream calls without knowing return structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 23 | 2026-07-28+ | v2 |
mcp_server.py does not implement MCP protocol. It prints a JSON status message and exits. No request/response loop, no tool invocation handler, no protocol version negotiation, no _meta field support. This is a non-functional stub.
No error handling or recovery guidance. If file routing fails, the tool provides no actionable error message or next steps for the LLM. Violates pattern:recovery-guide.