Loading ToolBench
MCP server that provides access to personal information and inventory data via tools and prompts
Single tool 'shampoo_available' has critical definition gaps. Tool name lacks action verb (should be 'get_shampoo_available' or 'list_shampoo_stock'). Description is minimal (8 words, 54 chars, below 10-char baseline). Input schema is empty object {} with no parameters documented. Output is unstructured string (file contents) with no schema definition. No error handling guidance beyond FileNotFoundError. Tool reads from hardcoded local file path, indicating development-only code not production-ready. No pagination, no structured response, no field documentation.
Give the Shampoo Stocks Available information
Tool name lacks action verb. 'shampoo_available' is a noun phrase; should be 'get_shampoo_available' or 'list_shampoo_stock' to signal the action to LLMs.
Input schema is empty object {} with no parameters. Tool accepts no parameters but this is not documented.
Description is 54 characters ('Give the Shampoo Stocks Available information'), below 10-char minimum and lacks WHAT/WHEN/WHY context. No guidance on when to call this tool vs alternatives.
Output schema not documented. Tool returns raw file contents as unstructured string. LLMs cannot parse or extract fields. Should return structured JSON with fields like {total_units: int, items: [{name, quantity, unit}], last_updated: string}.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 23 | 2026-07-28+ | v2 |
Hardcoded file path '/Users/ankitkumar/Downloads/...' indicates development code. Not portable across environments. Should use environment variables or configuration. Path traversal risk if file path becomes parameterized without validation.