MCP server for currency conversion and portfolio analysis with virtual thread support
Two tools with complete input schemas and descriptions, but significant gaps in output documentation and error guidance. Tool names follow verb_noun convention (convert_currency, summary_portfolio). Descriptions are adequate (60-90 chars) but lack context on when to use each tool or what to do on failure. Input schemas are well-formed with proper types and required fields. However, no output schemas are documented, LLMs cannot predict what fields to expect or plan downstream calls. Error handling exists but returns generic messages without recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations.
Conversion from one currency to another (with example exchange rates).
It converts assets in different currencies into a single target; gives the total value and the largest foreign exchange risk.
No output schemas documented. LLMs cannot predict response structure or plan chained calls. Both tools return text content only, document the exact format (e.g., 'Returns formatted string: "<amount> <from_currency> = <converted_amount> <to_currency>"').
Error messages lack recovery guidance. CurrencyException and generic exceptions return raw messages without suggesting next steps. Should return: 'Currency not found: USD. Try with ISO 4217 codes (USD, EUR, GBP)' or 'Service unavailable. Retry in 30 seconds.'
Tool descriptions lack context on when to use each. 'Conversion from one currency to another' does not explain: Is this for single conversions or batch? Does it cache rates? What currencies are supported? Add: 'Use for single currency conversions. Supports ISO 4217 codes. Rates updated hourly.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
No tool annotations despite both tools being read-only. Add readOnlyHint=true to both tool definitions so agents know these are safe to call without side effects.
Parameter descriptions lack format constraints. 'Source currency, e.g. USD' uses an example instead of a formal constraint. Replace with: 'Source currency as ISO 4217 code (3 uppercase letters, e.g., USD, EUR, GBP)' and add enum or pattern validation.