Burs-IA Utils

Países que usan una moneda (ISO 4217)

currency-countries

Read-onlyIdempotent

Lista los países y territorios cuyo campo de monedas en los datos countries-list incluidos contiene un código ISO 4217 (USD, EUR, XOF), con nombres en español e inglés y el nombre de la moneda según CLDR; refleja esa lista, no el curso legal. Cuándo: hay que listar los países que usan una moneda ISO 4217 dada con fuente citada. No para: devolver los datos de una moneda ISO 4217 (currency-info). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Lists the countries and territories whose currencies field in the embedded countries-list data includes an ISO 4217 code (USD, EUR, XOF), with English and Spanish names and the currency name from CLDR; reflects that list, not legal-tender status. When: the countries that use a given ISO 4217 currency have to be listed from a cited source. [EN completo / full EN: inputSchema.description]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "USD"
    },
    "name": "currency-countries"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	ISO 4217 currency code (COP, USD, EUR) (string; required; at least 3 chars; up to 3 chars).

Output Schema

Name	Required	Description	Default
`code`	No
`note`	No
`count`	No
`source`	No
`name_en`	No
`name_es`	No
`countries`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, but the description still adds real information beyond them: hard limits (64 KB JSON input, 1 s per call, 1 MB result), the determinism guarantee, and the important semantic caveat that the result reflects the embedded dataset rather than legal-tender status. The 'sin red, sin estado guardado' phrasing largely restates what the annotations already imply, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The Spanish block is front-loaded and well structured with labelled Cuándo / No para / Efectos secundarios / Determinista / Límites sections. It is somewhat bloated by full duplication into English, though the cross-reference '[EN completo / full EN: inputSchema.description]' avoids quoting the whole English text a third time.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with an output schema and full annotation coverage, the description covers everything an agent needs: the data source, the membership rule (currencies field includes the ISO code), the caveat about legal tender, the alternative tool, resource limits, and determinism. Return-value details are appropriately left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter and schema description coverage is 100%: the schema already documents 'code' as a 3-character ISO 4217 code with examples. The description restates the same examples (USD, EUR, XOF) without adding semantics such as case sensitivity or what happens for an unlisted code, so it meets but does not exceed the baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Lista los países y territorios cuyo campo de monedas ... contiene un código ISO 4217'), states the data source (the embedded countries-list), the returned fields (English/Spanish names plus the CLDR currency name), and the key caveat that it reflects that list rather than legal-tender status. It also explicitly contrasts itself with currency-info, so the agent can separate them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-clause ('hay que listar los países que usan una moneda ISO 4217 dada con fuente citada') and an explicit not-for clause naming the sibling to use instead ('No para: devolver los datos de una moneda ISO 4217 (currency-info)'). Both the inclusion and exclusion conditions are stated, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Burs-IA Utils tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?