Skip to main content
Glama

Compare countries

compare_countries
Read-only

Compares one measure across up to 20 countries, and names any differences in how the figures were counted, such as different periods.

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": {
      "iso2": "<iso2>",
      "measure": "<measure>"
    },
    "name": "compare_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
iso2YesTwo-letter country codes, such as PE, MX and CO.
measureYesThe measure to compare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context the annotations cannot: results flag differences in how figures were counted, such as differing reference periods, which tells the agent to expect comparability caveats rather than raw numbers. It stops short of describing the response shape or how missing countries are handled.

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?

A single sentence, front-loaded with the core action and bounded scope, with no filler. Slightly compressed phrasing ("names any differences") is efficient rather than wasteful.

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 two-parameter read tool with full schema documentation and no output schema, this covers what is needed to call it and hints at what comes back (figures plus counting-method notes). Only the concrete result shape and behavior for unavailable measures per country are left unstated.

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%, with the enum and the minItems/maxItems bounds already documented. The description usefully stresses "one measure" (the measure parameter is a single value, not a list) and repeats the 20-country cap, but adds no format or semantics beyond that, so the baseline of 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 gives a specific verb and resource ("compares one measure across up to 20 countries") plus an unusual scope detail: it also surfaces methodological differences in how figures were counted. The single-measure framing separates it from a generic record-lookup like get_country, though no sibling is named explicitly.

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 comparison context is implied clearly enough to pick the tool for multi-country work, but there is no explicit when-to-use versus when-to-use-instead guidance (e.g., use get_country for a single country, list_countries to enumerate valid codes). No exclusions or prerequisites are stated.

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