This server has critical definition gaps. Tool schemas are not visible in the source code, only tool names and brief descriptions are provided. The three tools (know_about_mospi_api, get_indicators, get_data) lack complete input/output schema documentation. Only get_indicators and get_data show partial parameter info; know_about_mospi_api has no schema at all. Descriptions are present but generic (10-80 chars), below the 50-200 char baseline for LLM-optimized tools. No error handling guidance, no output schema documentation, and no parameter validation rules are evident. The server appears to be a wrapper around an external MCP endpoint (https://mcp.mospi.gov.in/sse) rather than implementing tools directly, which means tool definitions are inferred rather than explicitly registered in this codebase.

• Add explicit input/output schemas to all tools in the MCP server definition. Document what fields get_indicators returns (e.g., indicator_id, sector, description) so agents can chain calls correctly.
• Expand tool descriptions to 50-200 characters. For know_about_mospi_api, explain: 'Discover available MoSPI datasets and API capabilities. Call this first to understand what data is available before searching for specific indicators.'
• Add parameter constraints: 'years' in get_data should specify min=1, max=50 (or appropriate bounds). Document the format of indicator_id (e.g., 'alphanumeric string, e.g. GDP_IND_001').
• Document output schemas with examples. E.g., get_indicators should return [{indicator_id: string, sector: string, description: string}]. Include chaining IDs (indicator_id) so agents can immediately call get_data.
• Add error handling guidance: 'If indicator_id is invalid, the tool returns a 404 with available sectors. If data is missing for a year, the tool returns null for that year rather than failing the entire request.'