Skip to main content
Glama

Country by ISO code

get_country
Read-onlyIdempotent

Returns one country by ISO alpha-2 code: its name, the names of its DSSR posts and State Department notes. Use get_countries to find the code from a name, and get_dssr_locations_by_country when the post codes are needed too. Returns no rates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country_iso_code": "<country_iso_code>"
    },
    "name": "get_country"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_iso_codeYesISO 3166-1 alpha-2 country code, e.g. PG for Papua New Guinea; ZZ stands for 'Other Foreign Localities', not a country. Resolve a country name to its code with get_countries (q=name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 closed-world, so the safety profile is covered. The description adds real behavioral value by naming the returned content and explicitly stating the tool returns no rates, which is a scope limit not encoded anywhere in the structured fields. It stops short of describing behavior for invalid or special codes, though the schema handles the ZZ case.

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?

Three short sentences with the output scope front-loaded and the routing guidance after it; no filler and no repetition. Every clause either describes the return value or redirects to a sibling.

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 single-parameter, read-only lookup with no output schema, naming the returned fields is the main thing needed and it does that. It leaves the exact shape of the notes/post-name fields implicit, but that is a minor gap given the tool's simplicity and the annotations.

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 property already documents the ISO 3166-1 alpha-2 format, the ZZ special case, and the get_countries resolution path. The description restates the alpha-2 requirement and the name-to-code lookup but adds no syntax or edge-case detail beyond the schema, so the baseline of 3 applies.

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 a specific verb and resource ('Returns one country by ISO alpha-2 code') and enumerates exactly what comes back: the country name, its DSSR post names, and State Department notes. That is enough for an agent to distinguish it from get_countries or get_dssr_locations_by_country without opening any 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 names two alternatives with the exact condition that selects each: get_countries when you need to resolve a name to a code, and get_dssr_locations_by_country when post codes are also required. It also sets a negative boundary ('Returns no rates'), steering the agent away from this tool for per-diem/rate work.

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