Single tool 'list_timezones' has a basic description but critically lacks a complete input schema in the visible source. The description is generic (47 chars) and provides minimal context for LLM selection. No output schema is documented. The tool is exposed via a remote HTTP MCP server (src/proxy.ts bridges to https://api.agishub.com/mcp), but the actual tool definition is not visible in the provided source, only a reference in src/try.ts.

• Add explicit JSON Schema for list_timezones input: { type: 'object', properties: { query: { type: 'string', description: 'Timezone query string (e.g., partial name or UTC offset). Returns matching IANA timezone identifiers.' } }, required: ['query'] }
• Expand tool description to 100 - 200 chars: 'Search for IANA timezone identifiers by partial name or offset. Returns a list of matching timezone names (e.g., Asia/Kolkata, America/New_York). Use this to resolve user-provided timezone names to standard identifiers before scheduling or converting times.'
• Document output schema: 'Returns { timezones: [{ name: string, offset: string, aliases?: string[] }], total: number }'
• Remove example values from parameter descriptions; use enum or pattern constraints instead. If query accepts free-form strings, state the format: 'Partial IANA timezone name or UTC offset (e.g., +05:30).'
• If the actual tool definition lives on the remote hub, publish a schema snapshot in this repo (e.g., tools.json) so consumers can validate locally without calling the hub.