Skip to main content
Glama

Find airports and city codes

find_airports
Read-onlyIdempotent

Find airports and city codes for your trip using Mubboo Flights. Search by place name or IATA code and choose the intended location when several suggestions match. Results identify locations; flight availability is checked separately.

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": {
      "query": "<query>"
    },
    "name": "find_airports"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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, non-destructive, closed-world), and the description adds genuinely new behavior: multiple suggestions may match and the caller must pick one, and results are location identifiers rather than availability. No return format or max-result behavior is described, but the added context is real.

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?

Three tight sentences, front-loaded with the action and ending with the scoping caveat. The branding phrase ('for your trip using Mubboo Flights') is the only mild filler.

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 simple two-parameter lookup with no output schema, the description covers purpose, input semantics, disambiguation behavior, and the boundary with flight availability. Only the 'language' parameter and result shape remain unaddressed.

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 0%, so the description must carry the load. It clarifies that 'query' accepts either a place name or an IATA code, which is valuable, but says nothing about the 'language' parameter or the accepted input constraints.

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

Purpose5/5

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

Specific verb+resource ('Find airports and city codes') with a clear scope distinction: results identify locations and flight availability is checked separately, which implicitly separates it from prepare_flight_search. An agent can place this tool without opening the schema.

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

Usage Guidelines4/5

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

Gives concrete usage context: search by place name or IATA code, and disambiguate when several suggestions match. It also implies the boundary with the flight-search flow, but never names the sibling tools or states an explicit when-not-to-use condition.

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