Aviasurf

Inspect cached route facts

route_facts

Read-onlyIdempotent

Summarize a cached fare sample in an interactive route profile: price statistics, airlines observed, travel duration, route distance, and city airports. Prices are per adult. Always link the returned search_url from a short label in the answer language, for example "Check live prices on Aviasurf"; never paste the raw URL as text. direct_seen means only that a nonstop option appeared in the sample; never infer that direct flights do not exist.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "route_facts"
  }
}

Input Schema

Name	Required	Description	Default
`locale`	No	Language locale for airport and airline names.	en
`market`	No	Two-letter country market. Set it only when the user explicitly requests a country market or local Aviasurf site; otherwise the service derives it from the departure country.
`origin`	Yes	Origin city or airport IATA code.
`currency`	No	Three-letter output currency. Set it only when the user explicitly requests a currency; otherwise the service derives it from the departure country.
`depart_date`	No	Optional exact departure date. Omit both date fields for the cheapest observations across the cached horizon; do not combine with depart_month.
`destination`	Yes	Destination city or airport IATA code.
`return_date`	No	Optional return date for a round trip.
`depart_month`	No	Optional departure month. Omit both date fields for the cheapest observations across the cached horizon; do not combine with depart_date.

Output Schema

Name	Required	Description	Default
`note`	Yes
`query`	Yes
`stats`	Yes
`currency`	Yes
`warnings`	No
`freshness`	Yes
`search_id`	Yes
`price_kind`	Yes
`request_id`	Yes
`search_url`	Yes
`updated_at`	Yes
`fallback_used`	Yes
`query_coverage`	Yes
`schema_version`	Yes
`fallback_reason`	Yes
`origin_airports`	Yes
`destination_airports`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: prices are per adult, the returned search_url must be surfaced as a labeled link, and the crucial caveat that direct_seen only means a nonstop appeared in the sample and must not be read as absence of direct flights.

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 sentences, front-loaded with the purpose and returned fields, then the two behavioral rules. Dense and mostly waste-free, though the direct_seen clause is packed into the same sentence as the linking rule rather than separated.

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 an output schema present and full schema description coverage, the description need not explain return shapes; it correctly focuses on purpose and interpretive caveats. The one remaining gap is sibling routing (when to prefer this over the live-price tools), which is left 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 100%, so the schema already documents all 8 parameters including the market/currency 'only when explicitly requested' rules and the depart_date vs depart_month exclusivity. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ('summarize') and resource ('a cached fare sample in an interactive route profile') and enumerates the returned facts (price statistics, airlines, duration, distance, city airports). It implies a cached-data scope distinct from live-search siblings, but never names an alternative tool, so an agent must infer the boundary with flight_prices/open_search.

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?

It gives strong output-handling rules (link search_url behind a label, never paste the raw URL, prices are per adult) but says nothing about when to choose this tool over flight_prices, flight_prices_filtered, or open_search. Usage is implied rather than routed.

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

All Aviasurf 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?