A simple MCP server that provides datetime functionality
Single tool with minimal definition quality. Tool name 'get-current-datetime' follows verb_noun convention (+), but description is extremely brief (28 chars, well below 50-200 char baseline for LLM-optimized descriptions). Input schema is empty object {} with no parameters, technically present but trivial. No parameter descriptions exist (N/A). Output schema is not documented; only inferred from code (returns text content). No error handling guidance. Tool is read-only and stateless, which is correct, but lacks the rigor expected even for simple tools.
Get the current date and time
Description is 28 characters, far below the 50-200 char baseline for LLM-optimized descriptions. LLMs cannot determine when/why to select this tool vs alternatives.
Output schema is not documented. LLMs cannot plan downstream tool calls or extract structured data without knowing the response format.
No error handling guidance. If the tool fails (e.g., system clock unavailable), the LLM has no recovery path.
Tool serves a trivial use case (current datetime). Most LLMs have built-in knowledge of current time; this tool adds minimal value and wastes a tool slot.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |