International Currency Exchange Service - provides real-time currency conversion from CNY to multiple international currencies
Single tool server with adequate but limited definitions. The 'exchange' tool has a properly registered schema with type constraints and enum values, which meets baseline requirements. However, descriptions lack depth beyond generic service declaration, and output schema is implicit in returned text rather than formally documented. Error handling exists but provides minimal recovery guidance. Schema completeness is solid (all params typed, constrained), but description quality falls short of A-grade standards (tool description is 43 chars, well below the 194-char average for A+ tools).
International Currency Exchange Service
Tool name 'exchange' lacks action verb prefix. Naming should follow verb_noun pattern (e.g., 'convert_currency' or 'get_exchange_rate') to help LLMs infer intent from name alone.
Tool description 'International Currency Exchange Service' is generic (43 chars, p10 baseline) and does not explain WHAT the tool does, WHEN to use it, or what the output represents. Should be 50-200 chars with concrete guidance.
Output schema is not formally documented. Tool returns hardcoded text format ('{amount} {fromCurrency} equals:\n{results}') with no structured field definitions. LLMs must parse unstructured output, risking errors.
Parameter 'fromCurrency' is constrained to only ['CNY'] but this limitation is buried in enum constraint, not explained in description text. LLMs may not understand why other currencies are unavailable.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 5 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 42 | - | v1 |
Error handling returns text-based error messages without recovery guidance. When calculation fails, response is 'Error processing exchange rate calculation: {message}' with no hint about what the LLM should try next.
No validation of amount parameter constraint (positive). If LLM passes negative or zero value, it silently succeeds (e.g., -100 CNY calculates normally). Should return explicit error: 'Amount must be positive (got: {value})'.