Loading ToolBench
A skill/service for checking if supplier restock is delayed based on transit days threshold
This server has a single tool 'check_delay' with severe definition gaps. The tool name lacks clarity and the parameter/output documentation is minimal. The description is generic (48 chars), and while a schema exists, it lacks critical contextual information. No error handling guidance is provided. The implementation is trivial (comparing transit_days > 7) but the definition quality does not meet even basic MCP standards.
Checks if supplier restock is delayed based on transit days
Tool name 'check_delay' is vague and does not start with a clear action verb. Does it check for delays, flag delays, or retrieve delay status? The name alone does not convey intent. Should be 'is_restock_delayed', 'check_restock_delay', or 'detect_supplier_delay'.
Tool description is too short (48 chars) and lacks actionable context. It does not explain WHEN to call this tool, what threshold triggers 'delayed', or what the user should do with the result. Should be 100-200 chars and include: the delay threshold (>7 days), use case (restocking decisions), and output semantics (is_delayed boolean).
Input parameter 'transit_days' has no description. LLMs cannot infer what value to pass or the valid range. Should describe: 'The number of days the shipment has been in transit (1-365). Higher values indicate potential delays.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
Output schema is not documented. The response appears to be {"is_delayed": boolean}, but this is inferred from the code, not formally specified. Tool consumers have no formal contract for the response structure.
No error handling or validation. The tool accepts any integer for transit_days but does not validate range (e.g., negative values, absurdly high values like 999999 days). No error guidance is provided if input is invalid.
Magic constant (7 days) hardcoded in the logic but not documented. LLMs and users cannot understand why 7 is the threshold. Should be parameterized or explained in the description: 'Delays are flagged when transit exceeds 7 days (standard lead time).'
No composition guidance. This tool returns a boolean flag but does not indicate what the next action should be if is_delayed=true. Should the agent trigger an alert? Search for alternative suppliers? The description should guide the LLM: 'If true, use trigger_restock_alert() to notify procurement.'