Skip to main content
Glama

National Capability Benchmark

Compare countries side by side

compare_countries
Read-onlyIdempotent

Two to 4 countries side by side on the nine dimensions, in the order you give them. The result is not sorted by score: the benchmark compares shapes and does not rank (D1).

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

Input Schema

NameRequiredDescriptionDefault
countriesYesISO3 codes or English names

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 cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's real contribution is output behavior: result order follows input order and is deliberately not sorted or ranked. That is genuinely useful non-obvious context, though it does not describe the result's overall shape.

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 short sentences, front-loaded with the core operation and followed by the one behavioral caveat. Nothing is redundant and no sentence could be dropped without losing information.

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 carries return-value burden and does disclose ordering and non-ranking, the most decision-relevant output traits. It does not sketch the result structure (per-country scores across the nine dimensions), which leaves a minor gap for a comparison tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameter's bounds and item type are already documented. The description still adds meaning beyond the schema by stating that the order of countries matters and is preserved, which the schema does not convey.

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 states a precise verb and resource ('Two to 4 countries side by side on the nine dimensions'), plus the count bounds and the scope of comparison, which clearly separates it from the single-country sibling get_country. An agent can tell what it produces without opening the schema.

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 'two to 4 countries side by side' framing makes the multi-country comparative use case clear, implicitly routing single-country lookups elsewhere. It does not, however, explicitly name an alternative or state when not to use it, so it stops short of full routing guidance.

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