Loading ToolBench
MCP server that provides system time information
Single tool with minimal quality attributes. The tool 'now_utc_iso' has a basic description and empty input schema, but lacks parameter documentation, output schema specification, error handling guidance, and composition context. The implementation is trivial (returns current UTC time) with no complexity to justify poor documentation. At 34 characters, the description falls below the 50-200 character optimal range for LLM-optimized tools and provides no context on WHEN or WHY to use this tool vs alternatives.
Show now system time in UTC ISO format
Description too brief (34 chars), below 50-character minimum. Lacks context on tool purpose and when to call it vs alternatives.
Input schema completely empty. Tool receives no parameters, but schema should document this explicitly (e.g., empty object with type 'object') rather than bare '{}'. Tool definition visibility is marginal, schema inferred from registration.
No output schema documented. LLMs need to know that response contains 'content[0].type=text' and 'content[0].text=ISO8601_string'. Without schema, downstream reasoning about output structure is unreliable.
No error handling or recovery guidance. What if Date() throws an error? What should the LLM do? No error classification (retryable vs fatal) provided.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 32 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 21 | - | v1 |
Tool name 'now_utc_iso' uses 'now' (vague) rather than action verb 'get_'. Better name: 'get_current_utc_time' or 'get_system_time_utc'. Current name does not clearly signal that this is a READ-ONLY getter.