Skip to main content
Glama

National Capability Benchmark

Read one country

get_country
Read-onlyIdempotent

One country's nine dimensions, each with score, confidence and its band, indicator count, coverage flag, trend, panel estimate where one exists, and links to the known limits that apply. Takes an ISO3 code or an English country name.

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": "<country>"
    },
    "name": "get_country"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesISO3 code (BRA) or English name (Brazil)
indicatorsNoAdd every observed indicator row: value, year and source

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 cover the safety profile (readOnly, idempotent, closed-world), yet the description still contributes real behavioral content by itemizing the returned fields and flagging that some fields are conditional ('panel estimate where one exists'). With no output schema present, that return-shape disclosure is doing genuine work.

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?

Two sentences, both front-loaded and free of filler, with the payload description leading and the input contract trailing. It is dense to the point of jargon ('band', 'panel estimate') but no sentence is wasted.

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 no output schema, the description covers the return shape and the accepted key format well enough to call it correctly. What is missing is guidance on the `indicators` flag and what the nine dimensions actually are, a minor gap given the schema already documents the parameters.

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%, so both parameters are already documented at the field level. The description merely restates the accepted input formats (ISO3 or English name) and says nothing about the `indicators` toggle, which is the one parameter where added meaning would have helped.

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 enumerates the exact payload of a single-country lookup (nine dimensions, score, confidence, band, indicator count, coverage flag, trend, panel estimate, limit links), and the title supplies the verb 'Read'. 'One country's' signals single-country scope as against the sibling compare_countries, though the description never names that alternative 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?

Usage is only implied: an agent can infer this is the per-country detail lookup, but there is no statement of when to prefer it over compare_countries or search_indicators. Nothing about the `indicators` flag or when it is worth enabling is offered as 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