Skip to main content
Glama

Get Country

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").

Input Schema

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

Output Schema

TableJSON 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. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "country_code": "US"
      +  },
      +  {
      +    "country_code": "GBR"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "admin_region": {
      +      "description": "Administrative region name",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "capital": {
      +      "description": "Capital city name",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "description": "World Bank country ID",
      +      "type": "string"
      +    },
      +    "income_level": {
      +      "description": "Income level classification",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "iso2": {
      +      "description": "ISO 3166-1 alpha-2 country code",
      +      "type": "string"
      +    },
      +    "latitude": {
      +      "description": "Capital city latitude coordinate",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "lending_type": {
      +      "description": "World Bank lending type",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "longitude": {
      +      "description": "Capital city longitude coordinate",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "name": {
      +      "description": "Full country name",
      +      "type": "string"
      +    },
      +    "region": {
      +      "description": "World region name",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "iso2",
      +    "name",
      +    "region",
      +    "admin_region",
      +    "income_level",
      +    "lending_type",
      +    "capital",
      +    "longitude",
      +    "latitude"
      +  ],
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
      -  {
      -    "country_code": "US"
      -  },
      -  {
      -    "country_code": "GBR"
      -  }
      -]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "admin_region": {
      -      "description": "Administrative region name",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "capital": {
      -      "description": "Capital city name",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "id": {
      -      "description": "World Bank country ID",
      -      "type": "string"
      -    },
      -    "income_level": {
      -      "description": "Income level classification",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "iso2": {
      -      "description": "ISO 3166-1 alpha-2 country code",
      -      "type": "string"
      -    },
      -    "latitude": {
      -      "description": "Capital city latitude coordinate",
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "lending_type": {
      -      "description": "World Bank lending type",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "longitude": {
      -      "description": "Capital city longitude coordinate",
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "name": {
      -      "description": "Full country name",
      -      "type": "string"
      -    },
      -    "region": {
      -      "description": "World region name",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "required": [
      -    "id",
      -    "iso2",
      -    "name",
      -    "region",
      -    "admin_region",
      -    "income_level",
      -    "lending_type",
      -    "capital",
      -    "longitude",
      -    "latitude"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "admin_region": {
      +      "description": "Administrative region name",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "capital": {
      +      "description": "Capital city name",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "description": "World Bank country ID",
      +      "type": "string"
      +    },
      +    "income_level": {
      +      "description": "Income level classification",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "iso2": {
      +      "description": "ISO 3166-1 alpha-2 country code",
      +      "type": "string"
      +    },
      +    "latitude": {
      +      "description": "Capital city latitude coordinate",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "lending_type": {
      +      "description": "World Bank lending type",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "longitude": {
      +      "description": "Capital city longitude coordinate",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "name": {
      +      "description": "Full country name",
      +      "type": "string"
      +    },
      +    "region": {
      +      "description": "World region name",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "iso2",
      +    "name",
      +    "region",
      +    "admin_region",
      +    "income_level",
      +    "lending_type",
      +    "capital",
      +    "longitude",
      +    "latitude"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "country_code": "US"
      +  },
      +  {
      +    "country_code": "GBR"
      +  }
      +]
  5. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing a safe read operation. The description adds the specific data returned but no additional behavioral traits like rate limits or auth requirements.

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, no redundancy, immediately states the resource and allowed inputs. Every sentence serves a purpose.

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?

The tool is simple (1 param) and has a rich output schema, so the description's detail on returned fields and code format suffices. No gaps for correct invocation.

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?

The schema's country_code description already fully documents the ISO code format with examples, and the tool description repeats this info, adding no new meaning. With 100% schema coverage, baseline of 3 is appropriate.

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 uses the verb 'Get' and specifies 'basic information about a country' with explicit fields (full name, region, income level, capital city, coordinates). This clearly distinguishes it from sibling tools like get_gdp or compare_countries that target different metrics or behaviors.

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

Usage Guidelines4/5

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

The description says to 'Use ISO 3166-1 alpha-2 or alpha-3 country codes,' providing clear parameter usage. However, it doesn't explicitly contrast with sibling tools or state when not to use it, though the focused field list implies its use case.

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.