Skip to main content
Glama

Find location

find_location
Read-only

Finds cities and airports by name or IATA/ICAO code and returns a ref for each. The other Mirai Flights tools take places as refs; a city ref covers all of the city's airports.

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_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYescity or airport name, IATA or ICAO code
languageNoresponse language; defaults to the client's Accept-Language, then en

Output Schema

NameRequiredDescriptionDefault
locationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false and idempotentHint=false, so the safety and openness profile is covered. The description adds real context beyond that: results are returned as refs, and a city ref aggregates that city's airports, which matters for downstream calls. It says nothing about ambiguous queries, no-match results, or the cost of open-world lookups, so it earns only partial credit.

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?

Two short sentences, zero filler, and the ordering is front-loaded: what it does first, then the ref contract that governs how the result is used. Nothing is repeated or padded.

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?

With annotations, full schema coverage, and an output schema, the description covers purpose, the ref contract, and the city-vs-airport aggregation rule. The only missing piece for a search-shaped, open-world lookup is what to expect on zero or multiple matches.

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 description coverage is 100%, so both parameters are already documented in the schema, giving a baseline of 4. The description's mention of name/IATA/ICAO matches the query field description almost verbatim and adds no meaning beyond it. The language parameter is not discussed at all.

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?

States a specific verb (finds), specific resources (cities and airports), the input keys (name or IATA/ICAO code), and the output (a ref for each). That is precise enough that an agent can distinguish it from the charter/empty-leg siblings without opening any 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?

Explicitly tells the agent that the other Mirai Flights tools consume places as refs, which makes this effectively a prerequisite step, and adds the useful selection rule that a city ref covers all of the city's airports. It stops short of stating when-not to use it or how to disambiguate multi-match results, so it is clear context rather than full when/when-not guidance.

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.