Skip to main content
Glama

Score a flight deal

score_flight_deal
Read-only

Rate a flight price from 0 to 100 against the typical fare for that route and cabin. Use when someone asks if a fare is a good deal.

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>",
      "price": "<price>"
    },
    "name": "score_flight_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination airport IATA code, e.g. LHR
fromYesOrigin airport IATA code, e.g. JFK
cabinNoCabin class. Defaults to economy.
priceYesRound-trip price in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / from / enum
      Added value: +[
      +  "JFK",
      +  "EWR",
      +  "LAX",
      +  "SFO",
      +  "ORD",
      +  "MIA",
      +  "BOS",
      +  "IAD",
      +  "IAH",
      +  "DFW",
      +  "ATL",
      +  "SEA",
      +  "DEN",
      +  "PHX",
      +  "MSP",
      +  "LHR",
      +  "CDG",
      +  "FCO",
      +  "BCN",
      +  "MAD",
      +  "AMS",
      +  "FRA",
      +  "DUB",
      +  "LIS",
      +  "ATH",
      +  "IST",
      +  "KEF",
      +  "NRT",
      +  "HND",
      +  "ICN",
      +  "SIN",
      +  "HKG",
      +  "BKK",
      +  "TPE",
      +  "DEL",
      +  "SYD",
      +  "DOH",
      +  "DXB",
      +  "GRU",
      +  "BOG",
      +  "LIM",
      +  "SCL",
      +  "MEX",
      +  "CUN"
      +]
    • addedInput schema / properties / to / enum
      Added value: +[
      +  "JFK",
      +  "EWR",
      +  "LAX",
      +  "SFO",
      +  "ORD",
      +  "MIA",
      +  "BOS",
      +  "IAD",
      +  "IAH",
      +  "DFW",
      +  "ATL",
      +  "SEA",
      +  "DEN",
      +  "PHX",
      +  "MSP",
      +  "LHR",
      +  "CDG",
      +  "FCO",
      +  "BCN",
      +  "MAD",
      +  "AMS",
      +  "FRA",
      +  "DUB",
      +  "LIS",
      +  "ATH",
      +  "IST",
      +  "KEF",
      +  "NRT",
      +  "HND",
      +  "ICN",
      +  "SIN",
      +  "HKG",
      +  "BKK",
      +  "TPE",
      +  "DEL",
      +  "SYD",
      +  "DOH",
      +  "DXB",
      +  "GRU",
      +  "BOG",
      +  "LIM",
      +  "SCL",
      +  "MEX",
      +  "CUN"
      +]
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish this is a safe, read-only, closed-world computation. The description adds that it compares against the 'typical fare for that route and cabin', which is useful context, but it says nothing about how the score is derived or how to interpret the result. With annotations covering the safety profile, a 3 is appropriate.

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 the core behavior front-loaded and the usage trigger immediately after. Zero filler.

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?

There is no output schema, but the description communicates the return value's nature (a 0-100 rating relative to typical fare), which covers the main gap. It could go further on interpretation thresholds, but it is sufficient for an agent to call the tool correctly.

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 every parameter, including the cabin default and USD round-trip semantics. The description adds no syntax or format detail 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 names a specific verb (Rate) and resource (a flight price/fare for a route and cabin) and states the output scale (0-100). It distinguishes itself well in substance from the sibling deal-listing tools, though it never explicitly contrasts with them.

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 concrete trigger: 'Use when someone asks if a fare is a good deal.' That is a clear when-to-use condition, but there is no when-not guidance or named alternative among the siblings.

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