MCP Time Server implemented in TypeScript providing time-related tools for getting current time and converting times between timezones
Two tools with clear verb-noun naming (get_current_time, convert_time) and basic descriptions. Input schemas are present with Zod validation and parameter descriptions. However, descriptions are generic (under 100 chars) and lack context about when to use each tool or what makes them distinct. Output schemas are not documented, callers cannot see the structure of TimeResult or TimeConversionResult. Error handling is minimal: generic try-catch blocks that wrap errors without recovery guidance. No parameter constraints (e.g., timezone format validation, time format examples) beyond the description text. Missing idempotency hints and dependency documentation.
Convert a time between different timezones
Get the current time in a specified timezone
Output schemas not documented. TimeResult and TimeConversionResult types are defined in timeService.ts but not visible in tool registration. LLMs cannot infer response structure (fields, types, ranges) and must guess what data is available for downstream operations.
Descriptions lack context and decision guidance. Both descriptions are under 100 chars and do not explain when to use get_current_time vs convert_time, what prerequisites exist (valid IANA timezone required), or what the response contains. LLMs cannot distinguish between tools or plan multi-step operations.
Error handling provides no recovery guidance. Errors like 'Invalid timezone: ...' are returned but do not suggest next steps (e.g., 'Call list_timezones() to see valid options'). Agents cannot self-correct and must retry blindly or ask the user.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | <=2025-11-25 | v2 |
Parameter descriptions embed example values ('America/New_York', 'Europe/London', 'HH:MM'). LLMs tend to reuse examples literally rather than adapting to context, causing failures when users provide different timezones or times. Should use formal constraints (regex pattern, enum) instead.
No idempotency or state-modification hints. Both tools are read-only (correct), but this is not declared via tool annotations (readOnlyHint). Agents cannot determine which tools are safe to retry without side effects.