Loading ToolBench
A simple MCP server for handling unix timestamps
Single tool with basic schema and description. Tool name 'iso8601_to_unix' lacks action verb prefix (should be 'convert_iso8601_to_unix'). Description is adequate (89 chars, within 10-1024 range) but generic. Input schema present with type but parameter description is minimal (18 chars, below 20-char threshold). No output schema documented. Error handling returns text responses but lacks structured guidance for LLM recovery. Tool is READ_ONLY and simple, but definition quality falls short of production standards.
Converts an ISO8601 date time string to a Unix timestamp (seconds since epoch)
Tool name lacks action verb prefix. 'iso8601_to_unix' should be 'convert_iso8601_to_unix' to signal intent clearly to LLMs.
Parameter description 'ISO8601 date time string to convert' is 39 chars but lacks format constraints, examples, or edge case guidance (e.g., timezone handling, precision).
Output schema not documented. LLMs cannot predict response structure (text content, error field presence, field names). Should document: {content: [{type: string, text: string}], isError?: boolean}.
Error responses return plain text without structured guidance. 'Error: ... is not a valid ISO8601 date time string' should suggest next steps (e.g., 'Valid formats: 2024-01-15T10:30:00Z, 2024-01-15').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
No idempotency or side-effect declaration. Tool is READ_ONLY but lacks explicit annotation (toolAnnotations=false). Should use readOnlyHint to signal safety to agents.