FerryFlight

get_estimate

Get a NON-BINDING ferry-flight price estimate between two airports for an aircraft. Returns a full fee breakdown, distance/flight-time, and a booking_url.

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>",
      "aircraft": "<aircraft>"
    },
    "name": "get_estimate"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Destination airport — ICAO/IATA/local code.
`date`	No	Optional departure date YYYY-MM-DD (a sooner date may add an urgency surcharge).
`from`	Yes	Origin airport — ICAO (KJFK), IATA (JFK), or local code.
`aircraft`	Yes	FAA model code (preferred — from search_aircraft), an N-number (N12345), an ICAO type (C172), or "make model".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key trait: the estimate is non-binding, so no booking or side effect is created. It also names the return payload (fee breakdown, distance/flight-time, booking_url). It stops short of stating auth requirements, whether pricing is cached/stale, or how firm the quote is beyond "non-binding".

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 tight sentences with no filler; the most decision-relevant caveat (NON-BINDING) is front-loaded and visually emphasized, and the return contents are summarized in the second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the returned parts (fee breakdown, distance/flight-time, booking_url). Combined with the fully documented four-parameter schema, an agent has enough to call this correctly without further context.

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 100% and each parameter already documents its accepted code formats, so the schema does the heavy lifting. The description only restates the origin/destination/aircraft relationship and adds no format or constraint detail beyond it, making the baseline 3 correct.

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 and resource — a ferry-flight price estimate between two airports for a given aircraft — plus the shape of what comes back (fee breakdown, distance/flight-time, booking_url). That is clearly distinct from every sibling (get_aircraft, get_airport, get_route, get_live_flights), none of which price a ferry leg.

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 capitalized "NON-BINDING" tells the agent this is a quoting/planning call rather than a commitment, which is meaningful usage framing. However, there is no explicit statement of when to prefer this over get_route (distance only) or when not to call it, so the guidance is implied rather than stated.

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

All FerryFlight tools Inspect

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

Need Help?