TimeMCP has 3 well-named tools with clear descriptions and documented input schemas. All tools follow verb_noun naming (get_, convert_, describe_) and include parameter type definitions. However, output schemas are not documented, the response structure is not visible in the source. Parameter descriptions are present but vary in detail. Notably, 'describe_time' has an exceptionally detailed description (450+ chars) that exceeds the 200-char baseline but compensates with genuine clarification of supported formats. Tool annotations (readOnlyHint) are correctly declared for all tools. No error handling guidance is present in descriptions, and some parameters lack constraints (timezone accepts free-form strings with no validation hints).

• Add documented output schema for each tool. For get_current_time, document: { timestamp: RFC3339 string, timezone: string, local_time: string, utc_offset: string }. For convert_time: { source_time: string, source_timezone: string, target_time: string, target_timezone: string }. For describe_time: { timestamp: RFC3339, description: string, perspective: string, candidates?: [...] }.
• Replace free-form timezone string with validation in descriptions: 'IANA timezone identifier (e.g. America/New_York, Europe/London, UTC). See https://en.wikipedia.org/wiki/List_of_tz_database_time_zones for valid values.'
• Add error handling guidance: 'If timezone is invalid, tool returns error with: Invalid timezone "<value>". Use standard IANA identifiers like America/New_York.'
• Replace empty string defaults in convert_time with explicit guidance in description: 'Defaults to system timezone if empty string provided.' Or use null in schema instead of empty string.
• Add examples of supported relative phrases in describe_time description as an enum in JSON Schema, not inline: ["now", "today", "tomorrow", "yesterday"] to help LLMs understand valid inputs without ambiguity.
• Document pagination or result limits if describe_time returns multiple candidates; if unbounded, state the maximum candidates returned.

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry