An MCP server that provides LLMs with current date and time context with timezone support.
Single tool with clear naming (get_current_datetime) and solid descriptions. Tool description is 165 chars (within 10-1024 baseline). Parameter 'timezone' has a 156-char description with examples. Input schema is properly typed as object with string property. However, output schema is completely undocumented, LLMs cannot predict the response structure. Error handling is present (McpError for invalid timezone, InternalError fallback) but lacks recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite being a read-only, idempotent operation. Missing pagination/limits (not applicable here) and response field documentation.
Get the current server date and time. Optionally specify a timezone (e.g., 'America/New_York', 'Europe/London', 'Asia/Tokyo'). Defaults to server's configured timezone or UTC.
Output schema completely undocumented. Tool returns text content but LLMs cannot predict structure (content array with type/text fields). No documentation of response format.
Error messages lack recovery guidance. Invalid timezone error states the problem but does not suggest next steps (e.g., 'Call list_timezones() to see valid options', though no such tool exists).
No tool annotations despite being read-only and idempotent. Should include readOnlyHint=true and idempotentHint=true in tool definition to signal safety to agents.
Parameter description includes example values ('America/New_York', 'Europe/London', 'Asia/Tokyo') which LLMs may reuse literally. Should use enum constraint or pattern instead.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |