fotmob-mcp has clear naming conventions (verb_noun pattern) and reasonable descriptions for most tools. However, parameter descriptions are sparse or missing entirely. The `fetch_fotmob_route` tool accepts a generic `params` object with no schema constraints, forcing LLMs to guess valid parameter names and types. Output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages. The server exposes a domain-specific API (FotMob sports data) but lacks the rigor expected for production agent tooling.

• Convert 'params' in fetch_fotmob_route to a typed object with per-route parameter schemas. Use discriminated unions or route-specific parameter types so LLMs know which params apply to each route.
• Document output schemas for all tools. E.g., get_route_catalog returns array of {key, path, description, params, notes}; fetch_fotmob_route returns {route, path, params, useCache, payload}.
• Add enum constraints for route_key parameter in fetch_fotmob_route listing all valid route keys (search_suggest, all_leagues, matches, etc.).
• Enhance error messages with recovery guidance. E.g., 'Unknown route key: xyz. Valid keys: search_suggest, all_leagues, matches, ...' or 'Missing required param matchId for route match_details.'
• Clarify tool selection in descriptions. E.g., 'Use get_match_details for convenience when you have a match ID or URL; use fetch_fotmob_route for low-level access to any FotMob route.'