Skip to main content
Glama

Datos de un país (capital, moneda, idiomas)

country-info
Read-onlyIdempotent

Devuelve los datos de un país buscado por código ISO 3166-1 o por nombre en español o inglés (sin importar tildes): nombres, capital, monedas ISO 4217, idiomas, prefijos telefónicos, zonas horarias IANA y continente, con su fuente. Cuándo: se necesitan datos de un país (capital, moneda, idiomas, prefijo telefónico, zonas horarias) de una fuente citada y no de memoria. No para: buscar países ISO 3166-1 alfa-2 por código o por nombre en español o inglés (iso-country-lookup). 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: Returns the facts of one country found by ISO 3166-1 code or by name in English or Spanish (accent-insensitive): names, capital, ISO 4217 currencies, languages, international calling codes, IANA time zones and continent, from embedded open data with its source. [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
countryYesCountry: ISO 3166-1 alpha-2 (CO) or alpha-3 (COL) code, or name in English or Spanish (Colombia, Alemania, Germany) (string; required; at least 1 chars; up to 80 chars).

Output Schema

NameRequiredDescriptionDefault
codeNo
alpha3No
sourceNo
capitalNo
name_enNo
name_esNo
part_ofNo
continentNo
languagesNo
timezonesNo
currenciesNo
matched_byNo
native_nameNo
calling_codesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country / examples
      Added value: +[
      +  "CO"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, idempotent, closed-world behavior, but the description adds concrete context: embedded open data with a source, no network access, no stored state, determinism, and limits (64 KB input, 1 s per call, 1 MB result). It does not contradict the annotations and meaningfully supplements them.

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 definition is front-loaded with purpose and enumerates the most useful details in a logical order. It is somewhat long due to bilingual duplication and a pointer to the full English copy in inputSchema.description, but each content block still carries substantive information.

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?

Given the output schema, comprehensive annotations, complete parameter description coverage, and one-parameter shape, the description is complete enough for correct selection and invocation. It covers source, determinism, side effects, and operational limits, leaving no major omission.

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?

Schema coverage is 100%, and the property description already documents alpha-2/alpha-3 codes, English/Spanish names, examples, and length constraints. The description repeats those accepted forms and mentions accent-insensitive matching, which is also reflected in the schema description, so it adds little new parameter meaning beyond the structured fields.

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 opens with a specific verb and resource: it returns facts for one country found by ISO code or English/Spanish name. It enumerates the returned fields (names, capital, currencies, languages, calling codes, time zones, continent, source) and explicitly names the sibling iso-country-lookup as not the right tool for that lookup role.

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 a clear 'Cuándo' condition (facts needed from a cited source rather than memory) and an explicit 'No para' exclusion pointing to iso-country-lookup. This is exactly the when/when-not/alternative routing guidance an agent needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources