Skip to main content
Glama

Find tracked fares for a route

find_route_fares
Read-only

Show the cheapest recent fares we track for an airport pair, by cabin, with the usual price and discount. Use when someone asks what a route costs right now.

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": "find_route_fares"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination airport IATA code, e.g. LHR
fromYesOrigin airport IATA code, e.g. JFK

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a safe read-only, open-world, non-destructive operation. The description adds useful behavioral context by saying the fares are recent, tracked, cheapest, and include usual price and discount, though it does not mention limits, freshness windows, or missing-route behavior.

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?

The description is two tight sentences, front-loads what the tool returns, and follows with the usage condition. There is no wasted text.

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?

For a simple two-parameter read-only tool with full schema coverage and annotations, the description is nearly complete. It explains the returned fare information but does not clarify output grouping by cabin or edge cases such as no tracked fares.

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%, with both from and to documented as IATA airport codes and constrained by enums, so the baseline is 3. The description reinforces the airport-pair concept but adds no new parameter-level detail 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 uses a specific verb and resource: it shows cheapest recent tracked fares for an airport pair, with cabin, price, and discount. It is clear enough to distinguish this from general deals or scoring tools, though it does not explicitly name any sibling tool.

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?

It gives a clear usage condition: use when someone asks what a route costs right now. It does not state exclusions or direct alternatives among the sibling tools, so it falls short of a 5.

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