Skip to main content
Glama

Aviationstack Countries

aviationstack_countries
Read-onlyIdempotent

Country reference with capital city, currency, etc.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo
country_iso2No

Output Schema

NameRequiredDescriptionDefault
dataNoArray of country objects
paginationNoPagination metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that — it does not mention pagination, filtering behavior, or result size limits implied by the 'limit' parameter.

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 short sentence, front-loaded with the resource and its key fields, with no filler. The vague 'etc.' is the only real waste, and it slightly undercuts an otherwise efficient statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be described, and annotations cover the safety profile. For a simple three-parameter reference lookup that is close to sufficient, but the total absence of parameter guidance and the undefined 'etc.' leave real gaps an agent must guess at.

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

Parameters2/5

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

Schema description coverage is 0% across all three parameters (limit, search, country_iso2), so the description carries the full burden and fails to compensate. It never mentions that country_iso2 filters by ISO code, that search does free-text matching, or what limit controls, leaving the agent to infer semantics from parameter names and examples only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as a country reference and names a couple of returned fields (capital city, currency), so the agent knows it looks up country data. However, there is no verb and the trailing 'etc.' leaves the scope undefined, so it does not clearly distinguish itself from sibling aviationstack_cities beyond the noun 'country'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as aviationstack_cities or airlines. The agent must infer from the tool name alone that this is for country-level lookups rather than city or airline lookups.

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.