Skip to main content
Glama
Sign In

FerryFlight

by com.ferryflighthub
OverviewDiscussionsAdmin

get_route

Great-circle distance + FAA preferred route + optional ferry planning (fuel stops, flying days) for an aircraft.

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>",
      "to": "<to>"
    },
    "name": "get_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination airport code.
fromYesOrigin airport code.
aircraftNoOptional aircraft for fuel-stop / flying-day planning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the disclosure burden and does describe the core computation plus the optional fuel-stop/flying-day branch. It does not cover error behavior, permissions, output format, or whether the route includes waypoints.

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?

The definition is a single dense sentence with no wasted wording, and the main outputs are front-loaded. It is efficient, though slightly more verb-oriented phrasing would make the action clearer.

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 no-annotation, no-output-schema computation tool, the description communicates the main outputs and optional planning mode. It remains incomplete regarding return structure and edge cases, so an agent would need to infer more than ideal.

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%, so all three parameters are already documented. The description reinforces that the aircraft parameter enables ferry planning, but it adds little meaning beyond the schema's own parameter descriptions.

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 names the specific outputs: great-circle distance, FAA preferred route, and optional ferry planning. It is clear what get_route returns, but it does not explicitly distinguish this tool from nearby siblings such as get_estimate.

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?

Usage is implied by the phrase 'optional ferry planning ... for an aircraft', which suggests passing an aircraft when ferry planning is desired. However, there is no explicit when-to-use guidance, no exclusions, and no comparison with sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FerryFlight toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources