Five tools with complete input schemas and descriptions. Naming follows verb_noun pattern (exchange_rates, gold_kijang_emas, policy_rate_opr, base_rate, bnm_endpoint). Descriptions are detailed (100-250 chars) and explain WHAT, WHEN, and WHAT IS RETURNED. All parameters have type definitions and descriptions. However, no output schemas are documented, LLMs cannot predict response structure. Parameter descriptions lack format constraints (e.g., 'YYYY-MM-DD' is stated but not formalized). base_rate has empty properties (no params), which is valid but underdocumented. Error handling is minimal, no recovery guidance or categorization. No tool annotations (readOnlyHint, etc.) despite all being READ_ONLY. Composition is sound: each tool has one responsibility, and bnm_endpoint provides escape hatch for undocumented endpoints.

• Add output schemas to all tools. Document the structure of BNM API responses (e.g., exchange_rates returns {data: {rates: [{currency, buy, sell, middle}]}, meta: {...}}). This enables LLMs to plan downstream operations and extract fields correctly.
• Add tool annotations: set readOnlyHint=true for all five tools in the tool definition. This signals to MCP clients that these tools are safe to call without user confirmation.
• Enhance error handling: catch HTTP errors and return structured error objects with actionable guidance. E.g., 'Currency not found: USD. Valid currencies: SGD, EUR, GBP, JPY, ...' or 'Date out of range: 2026-05-28. Historical rates available from 2010-01-01 to 2026-05-27.'
• Formalize parameter constraints in JSON Schema. Add pattern: '^\d{4}-\d{2}-\d{2}$' to the 'date' parameter. Add minLength/maxLength to 'currency' (3 chars, ISO code). Add minValue/maxValue to 'year' and 'month'.
• Improve base_rate documentation: add a description explaining it returns per-bank lending rates (BR, BLR, effective rate) for all Malaysian financial institutions. Clarify that no parameters are needed and it always returns the latest snapshot.