Skip to main content
Glama

Población de un país (Banco Mundial)

country-population
Read-onlyIdempotent

Devuelve la población total de un país (indicador SP.POP.TOTL del Banco Mundial, último año de los datos incluidos, CC BY 4.0) con el año y la fuente; el país se busca por código ISO 3166-1 o por nombre en español o inglés. Cuándo: se necesita la población de un país con su año y su fuente y no una cifra de memoria. No para: devolver los datos de un país buscado por código ISO 3166-1 o por nombre en español o inglés (country-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: Returns the total population of a country (World Bank indicator SP.POP.TOTL, latest year in the embedded data, CC BY 4.0) with the year and source; the country is found by ISO 3166-1 code or by name in English or Spanish. When: the population of a country is needed with its year and source instead of an estimate from memory. [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
noteNo
yearNo
sourceNo
name_enNo
name_esNo
indicatorNo
matched_byNo
populationNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, but the description goes further by stating no network access, no stored state, determinism, and hard limits (64 KB input, 1 s per call, 1 MB result) — operational constraints the annotations do not carry. It rests just short of 5 because the read-only and determinism statements partly restate the hints.

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?

Front-loaded statement of what is returned, then purpose/labels for when-not, side effects and limits — every block is scannable. It loses a point for the truncated, self-referential tail ('[EN completo / full EN: inputSchema.description]') and for re-listing the accepted country forms that the schema already carries.

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?

With a single required parameter, full schema coverage, rich annotations and an output schema, nothing an agent needs is missing. The description adds the data vintage, license, alternative routing and operational limits, so failure modes are covered.

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 schema already documents that 'country' accepts ISO 3166-1 alpha-2/alpha-3 or an English/Spanish name, so the description largely repeats it. It adds the useful point that the result is the latest available year, but that is output semantics rather than parameter meaning.

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?

States a specific verb and resource (returns total population), names the exact World Bank indicator, and specifies the data vintage and license. It also explicitly names the sibling it replaces (country-info), so an agent can disambiguate 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?

Provides an explicit 'Cuándo' trigger (population with year and source, not an estimate from memory) and a 'No para' exclusion routing to country-info. Both the when and the when-not are stated with the alternative named.

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