This is a NestJS backend exposing 4 currency conversion tools via HTTP REST endpoints, not a native MCP server. Tool definitions are inferred from controller method signatures and Swagger annotations rather than explicit MCP tool registration. All 4 tools have basic descriptions (40-60 chars) and input schemas with type info, but descriptions lack LLM-optimization guidance (when to use, prerequisites, what it returns). Parameter descriptions are present but minimal. No output schemas documented. No error handling guidance. Transport is unknown, appears to be HTTP REST, not MCP protocol. This is a currency API wrapped as tools, not a production MCP server.

• Implement a native MCP server using the official MCP SDK (e.g., @modelcontextprotocol/sdk-nodejs). Register tools explicitly with tool_call handlers, not via REST controller inference.
• Expand tool descriptions to 100-150 chars following the pattern: 'Get [what]. Use this to [when]. Returns [structure]. Requires [prerequisites].' E.g., 'Get list of supported currency codes and metadata. Use this before calling getRates to validate currency codes. Returns array of {code, name, symbol}.'
• Document output schemas for each tool. Add a 'Returns' section in the description or a separate schema field showing the response structure (e.g., {rates: {EUR: 0.92, GBP: 0.79}, base: 'USD', date: '2024-01-15'}).
• Add error handling guidance: 'If currency code is invalid, returns 400 with message "Invalid currency: {code}. Call getCurrencies() to see valid codes."' This enables LLM self-correction.
• Add constraints to date parameters: 'Date in YYYY-MM-DD format. Must be a past date (not future). Historical data available from 2015-01-01 onwards.' Use enum or pattern in schema.