Skip to main content
Glama

Airports Worldwide: Airports in a country

airports__country
Read-onlyIdempotent

Airport counts by type, the large airports and the regions for a country. Free within the daily allowance, then $0.001 USDC per call via x402.

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": "airports__country"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYes2-letter country code

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description adds meaningful context by disclosing the cost model (free within daily allowance, then $0.001 USDC per call via x402) and summarizing return content, which is valuable for an agent managing paid calls.

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, no wasted words. The first sentence is slightly awkward in phrasing but front-loads the core data description; the pricing clause follows succinctly. Overall appropriately sized for the tool's simplicity.

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

Completeness5/5

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

Given the low complexity, full schema description coverage, rich annotations, and an output schema, the description is complete enough. It adds pricing context and a brief return summary; no critical missing piece would prevent correct invocation.

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 description coverage is 100% (the single 'country' parameter is documented as a '2-letter country code'). The description adds no additional parameter meaning, so the baseline score 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 states the resource and scope: airport data aggregated by country, including counts by type, large airports, and regions. It is clear what data is returned, but it does not explicitly contrast this tool with siblings like airports__airport or airports__search, leaving the agent to infer when this aggregate view is preferable.

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?

No when-to-use or when-not-to-use guidance is provided. The description only describes the data returned and the pricing model; it never names alternatives or conditions under which this tool should be chosen over the many sibling airport tools.

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