Skip to main content
Glama

price_flight

Confirm live price and availability for a specific flight offer before booking; returns the merchant artifact and payment receipt.

Instructions

Confirm the live price and availability of a specific flight offer before booking. Costs $0.003 per call, paid in USDC over x402 to x402-flight-search. Returns the merchant's artifact and the payment receipt.

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": {
      "offerId": "<offerId>"
    },
    "name": "price_flight"
  }
}

Input Schema

NameRequiredDescriptionDefault
railNoPayment rail for this call. Overrides the configured default (auto). auto = whichever rail this agent holds a key for.
offerIdYesofferId from search_flights

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A4.2/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 well: it discloses the per-call cost ($0.003), the payment mechanism (USDC over x402 to x402-flight-search), and the return contents (merchant artifact plus payment receipt). It omits failure/expiry behavior for stale offers and whether the charge applies on a failed lookup.

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 front-loaded sentences with no filler: the first states purpose and timing, the second states cost, payment path, and return value. Every sentence earns its place.

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?

No output schema exists, so the description must describe returns, and it does ('merchant's artifact and the payment receipt'). Cost and payment routing are covered for a 2-parameter tool; only edge-case behavior on failed or expired offers is left unstated.

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 both parameters (offerId, rail) are documented in the schema itself, including the rail enum values. The description adds only the implicit link between offerId and search_flights, so it does not meaningfully exceed the schema baseline.

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 — 'Confirm the live price and availability of a specific flight offer' — and positions it in a workflow ('before booking'), which clearly separates it from search_flights, whose offerId this tool consumes.

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?

The phrase 'before booking' gives a clear trigger condition for calling this tool, and the schema reference to 'offerId from search_flights' implies the upstream step. It does not state when NOT to call it or name an alternative explicitly, 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.