The server defines 16 tools with consistent verb-noun naming (get_*, search_*) and reasonable descriptions. However, all tools lack documented output schemas, the codebase shows tools return serde_json::Value or typed structs, but the MCP tool registration does not expose response schemas. Parameter descriptions are present but minimal (10-50 chars), below the 72-char baseline for production quality. All tools are read-only, limiting the severity of missing error handling for state changes. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are declared despite the risk profile being well-understood. The schema definitions are present for inputs but lack detail (no min/max constraints on numeric params, no enums for multi-choice fields like item_type). Composite tools like search_items accept item_type as a free string rather than an enum, inviting hallucinated invalid values.

• Document output schemas for all tools in MCP registration. For each tool, add a 'returnType' or 'response' field showing the JSON structure. Example for get_users: { 'type': 'array', 'items': { 'type': 'object', 'properties': { 'id': { 'type': 'string' }, 'name': { 'type': 'string' }, ... } } }. This allows LLMs to extract the user_id field from get_users and pass it to get_user_details.
• Convert item_type parameters to enums in get_items_by_person, get_items_by_genre, and search_items. Extract valid ItemType values from the Rust enum and expose them as MCP enum schema. E.g., 'item_type': { 'type': 'string', 'enum': ['Movie', 'Series', 'Episode', 'MusicArtist', ...], 'description': 'The item type filter: Movie, Series, Episode, or MusicArtist.' }.
• Add min/max constraints to numeric parameters. E.g., 'limit': { 'type': 'integer', 'minimum': 1, 'maximum': 100, 'description': 'Number of items to return (1 - 100, defaults to 50).' } and 'page': { 'type': 'integer', 'minimum': 1, 'description': 'Pagination page number (1-indexed).' }.
• Expand parameter descriptions to 50 - 100 characters, including constraints and use cases. Example: 'page' → 'Pagination page number (1-indexed; defaults to 1). For results > 50 items, iterate page to fetch subsequent batches.' This guides LLM pagination logic.
• Disambiguate get_jellystats_item_details and get_jellyfin_item_details by renaming to get_item_activity_stats (returns playback analytics from JellyStats) and get_item_metadata (returns metadata like genres and cast from Jellyfin). Clearer intent prevents tool selection errors.

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

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