Skip to main content
Glama

Asia Miles Calculator

Get Direct Airline Routes

get_direct_routes
Read-only

List airlines operating direct flights from an origin airport (optionally filtered to a destination airport) with seasonality.

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": {
      "from": "<from>"
    },
    "name": "get_direct_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional destination 3-letter IATA code
fromYesOrigin 3-letter IATA code
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe read, so the description's main added value is disclosing that results carry seasonality information. It says nothing about pagination, the effect of the limit cap, or what an empty result means, which is a gap given there is no output schema to fall back on.

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?

A single sentence, front-loaded with the operation and resource, with the optional filter and the seasonality qualifier folded in cleanly. No redundant or filler phrasing.

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?

For a simple read-only lookup this covers the core operation, but with no output schema the description is the only place explaining return values and it does so only loosely ('airlines ... with seasonality'). The undocumented limit parameter and absent return-shape detail leave the definition adequate rather than complete.

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 coverage is 67%: 'from' and 'to' are documented as 3-letter IATA codes, and the description correctly signals that 'to' is optional. The third parameter, 'limit' (default 30, max 50), receives no mention anywhere, so the description neither compensates for that gap nor adds meaning beyond the 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 ('List') and a precise resource ('airlines operating direct flights from an origin airport'), plus the optional destination narrowing and the seasonality dimension. An agent can tell this is a route-lookup tool rather than an airport lookup or mileage calculator, though no sibling is named explicitly.

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 parenthetical '(optionally filtered to a destination airport)' makes the conditional usage of the second parameter clear, which is genuinely useful. However there is no statement of when to prefer this over search_airports or calculate_asia_miles, nor any prerequisite or exclusion 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.

Resources