Skip to main content
Glama

Get a country

get_country
Read-only

Gives one country's figures, scam types, money returned and sources, from its two-letter code such as PE.

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

Input Schema

NameRequiredDescriptionDefault
iso2YesThe two-letter country code, such as PE for Peru.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, establishing a safe read operation. The description adds useful behavioral context by listing the return content (figures, scam types, money returned, sources), which is valuable since there is no output schema. It does not cover error behavior or rate limits, but for a simple read tool this is acceptable.

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?

The description is a single, front-loaded sentence that states the action, the return categories, and the input format without any filler. Every clause contributes useful 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?

Given the tool's simplicity (one required parameter, read-only, no output schema), the description covers the purpose, return content, and input format adequately. It does not describe error handling for invalid codes or the exact response structure, but those are minor gaps for a straightforward get-by-id tool with annotations covering safety.

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?

The schema description coverage is 100%, so the single parameter is fully documented in the schema itself. The description repeats the example ('such as PE') without adding new meaning or constraints beyond what the schema already provides. Baseline score of 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb ('Gives') and resource ('one country's figures, scam types, money returned and sources') with the input format ('two-letter code such as PE'). It clearly implies retrieval of a single country's data, which distinguishes it from siblings like list_countries or get_world, but it does not explicitly name those alternatives.

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 implied by 'one country's ... from its two-letter code,' suggesting it is for fetching a single country by code. However, there is no explicit guidance on when to use this tool versus alternatives like get_scam_type, get_source, or compare_countries, nor any exclusions or prerequisites.

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