SRG SSR MCP Server demonstrates solid definition quality with 15 well-structured tools across weather, video, audio, EPG, and political data domains. All tools have clear, action-verb names (srgssr_weather_search_location, srgssr_video_get_shows, etc.) that follow verb_noun convention. Descriptions are concise (30-60 chars) and state the primary action. Input schemas are present and properly typed with descriptions for all parameters. However, output schemas are not explicitly documented in the source code, the server returns structured data but the response format is not formally declared. Parameter enums (business_unit values: srf, rts, rsi, rtr, swi) are well-constrained. Error handling is minimal; no recovery guidance or classification visible. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present despite all tools being READ_ONLY. Pagination is supported on list tools (page_size parameter) but total count / next_cursor not documented in output.

• Document output schemas for all tools. For list tools (get_shows, get_episodes, etc.), explicitly declare: returned fields, data types, pagination metadata (page_number, total_count, has_next_page or next_cursor). Example: 'Returns a list of show objects with fields: id (string), title (string), description (string), episode_count (integer).'
• Add tool annotations in the MCP server registration. Since all 15 tools are READ_ONLY, add `readOnlyHint: true` to each tool definition. This signals to intelligent clients that tools are safe to call without user confirmation.
• Enhance parameter descriptions with explicit constraints. For business_unit: 'One of: srf, rts, rsi, rtr, swi (case-sensitive).' For latitude/longitude: 'Decimal degrees; -90 to +90 for latitude, -180 to +180 for longitude.' For page_size: 'Number of results per page; default 20, maximum 100.'
• Add error recovery guidance to tool descriptions. Example for weather tools: 'Returns HTTP 400 if coordinates are out of bounds. Returns HTTP 404 if no forecast data available for the location. Retry with nearby coordinates or use search_location to validate the location first.'
• Document pagination behavior. For tools accepting page_size, state: 'Returns a results array and next_cursor field. If next_cursor is null, all results have been returned. To fetch the next page, pass next_cursor value in a subsequent call.' Or if using offset pagination: 'Supports offset/limit pagination. Total results count is returned; if (offset + page_size) < total, more results are available.'

Inferred effective spec: <=2025-11-25.

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