Skip to main content
Glama

Find country code and posts

get_countries
Read-onlyIdempotent

Resolves a country name to its ISO alpha-2 code and lists the names of its DSSR posts; q matches the country name case-insensitively ('papua' finds PG). Use it before any tool that needs a country code. ZZ stands for Other Foreign Localities, not a country. Returns no rates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch by country name
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is narrower. It adds real behavior beyond them: case-insensitive substring matching ('papua' finds PG), the ZZ sentinel meaning, and an explicit negative scope ('Returns no rates'). It says nothing about ordering or how limit/offset paginate the result set.

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, front-loaded with what the tool returns, then the usage rule, then edge-case and scope notes. Every sentence carries distinct information; nothing is repeated from the schema or annotations.

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?

With no output schema, the description correctly states the return shape (code plus post names) and what is not returned (rates). The main omission is pagination behavior for limit/offset given the 300-item ceiling, which matters for an agent enumerating countries.

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 only 33% — only `q` is documented in the schema, and the description usefully adds case-insensitivity and a worked example for it. But `limit` and `offset` are explained nowhere, so the description does not compensate for the coverage gap on two of three parameters.

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: resolves a country name to its ISO alpha-2 code and lists DSSR post names. The ZZ carve-out ('Other Foreign Localities, not a country') further pins the resource semantics, and the scope note 'Returns no rates' separates it from the many rate/per-diem siblings.

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?

Gives an explicit ordering rule: 'Use it before any tool that needs a country code,' which is exactly the guidance an agent needs in a list full of get_*_by_country siblings. It stops short of naming alternative lookup tools (e.g. get_country, get_dssr_locations_by_country) so the agent must infer the distinction itself.

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