MCP server that provides current date/time and geographic location information based on public IP address
Both tools have minimal definitions. Descriptions are present but extremely brief (under 100 chars each). No input schemas are visible, both tools declare empty input objects `{}`. No output schemas are documented. No parameter descriptions exist (there are no parameters). Error handling is minimal: get_my_location catches exceptions generically and returns a string, but provides no recovery guidance. No tool annotations (readOnlyHint, etc.). The server uses FastMCP but does not leverage structured output or proper schema definition.
Returns the current system date and time.
Returns your public IP address and estimated geographic location (via IP). Uses the ipinfo.io free API.
No input schemas defined. Both tools declare empty input `{}` with no JSON Schema structure, type definitions, or constraints.
Descriptions are too brief (under 100 chars). 'Returns the current system date and time' and 'Returns your public IP address and estimated geographic location (via IP)' lack context on WHEN to use these tools, what format is returned, or any prerequisites. Baseline: 194 chars average for A+ tools.
No output schemas documented. LLMs cannot plan downstream calls or extract structured data. Both tools return plain strings with emoji formatting, but no schema declares the response structure.
Error handling in get_my_location is generic. Catches all exceptions and returns 'Failed to get location: {e}', no recovery guidance, no categorization (retryable vs fatal), no actionable next steps for the LLM.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | <=2025-11-25 | v2 |
No tool annotations. Tools lack readOnlyHint, destructiveHint, or idempotentHint. Both are read-only and idempotent, but this is not declared in the schema.