Three well-named, read-only tools with clear descriptions (avg 180 chars, within baseline 194). All tools have proper JSON Schema with typed parameters. exchange_rate includes a required parameter with description. However, output schemas are completely undocumented, LLMs cannot plan downstream operations or extract fields. No error handling guidance, no pagination despite potential for large result sets (exchange_rates returns all currencies). Parameter descriptions lack format/constraint details (e.g., 'key' should specify ISO 4217 format, valid range). No tool annotations (readOnlyHint present but not declared). Descriptions are good but could be more LLM-optimized per pattern:tool-description baseline.
Current Bank of Israel representative exchange rate for a single currency vs the Israeli Shekel (ILS), by 3-letter ISO code. Returns currentExchangeRate (shekels per `unit`), currentChange (%), unit, and lastUpdate. Note `unit` (e.g. JPY is per 100). Example keys: USD, EUR, GBP, JPY, CHF, CAD, AUD.
All current Bank of Israel representative exchange rates vs the Israeli Shekel (ILS). Returns one entry per currency with currentExchangeRate (shekels per `unit` of the foreign currency), currentChange (% vs previous), unit (1 for most, 100 for some like JPY — per-1 rate = currentExchangeRate / unit), and lastUpdate. Use this for a snapshot of all available currencies.
The current Bank of Israel policy interest rate (% per annum). Returns currentInterest (the rate), nextInterestDate (date of the next rate decision), and lastPublishedDate.
Output schemas completely undocumented. LLMs cannot infer response structure (fields, types, nesting). Violates pattern:tool baseline: '100% of A+ tools have documented return types.' Without output docs, agents cannot chain tools or extract specific fields reliably.
Parameter 'key' in exchange_rate lacks format constraint. Description says '3-letter ISO currency code' but does not specify ISO 4217, valid range, or case-sensitivity rules.
No error handling guidance. If exchange_rate receives an invalid currency code, the tool throws a raw HTTP error. Per pattern:recovery-guide, errors must tell the LLM what to do next: 'Currency not found. Try exchange_rates() to see available codes.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
exchange_rates may return hundreds of currencies without pagination. Per pattern:paginated-result and mxe:enforce-result-limits, large result sets blow context windows. Tool should accept limit/offset and return total count.
Tool annotations missing. All three tools are read-only (no side effects), but readOnlyHint is not declared in schema. Per current spec (2026-07-28), tool annotations enable agents to reason about safety and retry logic.