Skip to main content
Glama

Aviationstack Cities

aviationstack_cities
Read-onlyIdempotent

Look up cities and their primary airport from the Aviationstack database by free-text name, IATA city code (e.g. NYC), or ISO country code.

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": {
      "iata_code": "NYC"
    },
    "name": "aviationstack_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo
iata_codeNoCity IATA code (e.g. "NYC" for all NYC airports)
country_iso2No

Output Schema

NameRequiredDescriptionDefault
dataNoArray of city objects
paginationNoPagination metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/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 covered. The description adds that results are city records with their primary airport, which is useful return-shape context, but says nothing about auth, rate limits, or pagination behavior.

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 front-loaded sentence with the resource first and the lookup keys after. It is tight, though "from the Aviationstack database" is low-value filler when the tool name already implies the source.

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?

An output schema exists, so return values need not be explained, and the lookup keys are covered. However, with zero required parameters, the description never says what happens when no filter is supplied (all cities? default limit?), which is the main behavioral question an agent would have before calling.

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 only 25% (just iata_code is documented), so the description has to compensate, and it does: it maps free-text name to search, IATA city code to iata_code, and ISO country code to country_iso2. Only limit is left unexplained, so the description carries most of the semantic load for a low-coverage schema.

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 gives a specific verb and resource ("look up cities and their primary airport") plus the backing source ("Aviationstack database"), which separates it from sibling tools like aviationstack_countries and airports. It stops short of naming an alternative explicitly, so it is clear but not sibling-differentiating at the top level.

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?

The three lookup modes (free-text name, IATA city code, ISO country code) imply how to call the tool, but there is no explicit statement of when to prefer it over aviationstack_countries or airports. No exclusions, prerequisites, or fallback guidance are given.

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.