Skip to main content
Glama

Worldbank Get Country

worldbank_get_country
Read-onlyIdempotent

Get basic information about a country: full name, region, income level, capital city, and coordinates. Use ISO 3166-1 alpha-2 or alpha-3 country codes (e.g., "US", "GBR", "IN").

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": {
      "country_code": "US"
    },
    "name": "worldbank_get_country"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYesISO country code (2 or 3 letters, e.g., "US", "GBR", "CN")

Output Schema

NameRequiredDescriptionDefault
idYesWorld Bank country ID
iso2YesISO 3166-1 alpha-2 country code
nameYesFull country name
regionYesWorld region name
capitalYesCapital city name
latitudeYesCapital city latitude coordinate
longitudeYesCapital city longitude coordinate
admin_regionYesAdministrative region name
income_levelYesIncome level classification
lending_typeYesWorld Bank lending type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and statelessness profile is fully covered without prose. The description adds only the shape of the payload (the five attributes returned), and an output schema exists anyway, so it contributes little beyond annotations; nothing is said about behavior for an invalid or unknown country code.

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

Conciseness5/5

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

Two sentences, zero filler, with the capability and its returned fields front-loaded before the input-format note. Every clause earns its place.

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

Completeness4/5

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

For a one-parameter, read-only lookup with full annotation coverage, an output schema, and 100% schema description coverage, the description supplies everything an agent needs to select and invoke it. The only residual gap is edge-case behavior on an unrecognized country code, which is minor.

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 description coverage is 100% and the single parameter already documents the ISO 2- or 3-letter format with examples. The description restates that same format constraint with its own examples, adding emphasis but no new meaning such as case sensitivity or ambiguity resolution for invalid codes, so the baseline 3 applies.

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

Purpose4/5

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

The description opens with a specific verb+resource ("Get basic information about a country") and enumerates the returned fields (full name, region, income level, capital, coordinates), which implicitly separates it from comparative siblings like compare_countries or metric siblings like get_population. It stops short of naming any sibling explicitly, so it falls just below the top mark.

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

Usage Guidelines3/5

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

The only guidance is on input format ("Use ISO 3166-1 alpha-2 or alpha-3 country codes"), which is parameter-level rather than when-to-use. There is no statement of when to prefer this over compare_countries, entity_profile, or country-specific metric tools, and no exclusions; usage is only inferable from the tool's obvious lookup nature.

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.