Loading ToolBench
Server has 4 tools with basic descriptions but significant quality gaps. Tool naming is inconsistent (readme_first vs check_conventions_setup vs get_convention_file vs development_workflow_prompt). Most tools lack input parameter descriptions, only get_convention_file and development_workflow_prompt have documented parameters. Schemas are minimal (mostly empty objects or single string params). No output schemas documented. Error handling returns plain strings without recovery guidance. No tool annotations (readOnlyHint, etc.). The resource-based tool (get_convention_file) is unusual for MCP and not properly integrated with tool composition patterns.
Verify that the chop-conventions repository is properly set up and accessible.
Generate a prompt for development tasks that incorporates chop conventions. Args: task: Description of the development task to perform
Access specific convention files from the chop-conventions repository. Available files: - clean-code.md - clean-commits.md - running-commands.md - a_readme_first.md
Returns the essential development instructions from ~/gits/chop-conventions/dev-inner-loop. This includes: - Clean code practices - Clean commit guidelines - CLI usage tips and error handling - Development workflow recommendations This should be the first command run when starting development work.
Inconsistent tool naming convention. 'readme_first' uses snake_case but lacks action verb; 'check_conventions_setup' is verbose; 'development_workflow_prompt' is a prompt, not a tool action. Names should start with clear verbs (get_, list_, verify_) to help LLMs infer intent.
No output schemas documented. Tools return plain strings; LLMs cannot parse structure or extract fields for downstream calls. Responses should be structured JSON with typed fields (e.g., {status: string, files: string[], errors: string[]}).
Error handling returns plain text without recovery guidance. Errors like 'Error: Could not find chop-conventions...' do not tell the LLM what to do next. Should include actionable steps: 'Repository not found at ~/gits/chop-conventions. Please clone it: git clone <url> ~/gits/chop-conventions'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
get_convention_file is registered as a resource (@mcp.resource) rather than a tool. Resources are for static content discovery; this should be a tool with file_name parameter. Mixing resource and tool patterns confuses composition.
development_workflow_prompt is a prompt, not a tool. It returns a static template string, not actionable output. If the intent is to guide task execution, this should be a system prompt or context, not a callable tool. If it should generate dynamic prompts, it needs structured output and clearer semantics.