Skip to main content
Glama

Travel airport (30 sats L402 or $0.025 USDC x402)

get_travel_airport
Read-only

One US airport (airport=SFO required): FAA delay/closure events plus current NOAA weather and NWS alerts. Not for navigation. Not endorsed by the FAA or NOAA. Price: 30 sats (Lightning) or $0.025 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"travel_airport","data":{"coverage":"us","source":"faa_nas_status","airport":{"iata":"SFO","icao":"KSFO","name":"San Francisco Intl","state":"CA","lat":37.6188,"lon":-122.375},"delays":{"has_published_event":true,"events":[{"airport":"SFO","type":"ground_delay","reason":"wind"}]},"weather":{"conditions":{"text":"Windy","temperature_f":58.0}},"alerts":{"coverage":"us","source":"noaa_nws","count":0,"alerts":[]},"not_for_navigation":true},"metadata":{"cost_sats":30}} Pay: Call it, get HTTP 402 (or MCP payment_required) with a Lightning invoice and macaroon, pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. Or pay in USDC on Base via x402: sign the 402's x402 requirement (PAYMENT-REQUIRED header, or accepts in the JSON body) and retry with the PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header; only a 200 is settled.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_travel_airport"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlias of airport.
iataNoAlias of airport.
icaoNoAlias of airport.
airportNoUS airport IATA (SFO) or ICAO (KSFO) code. Required for get_travel_airport; optional filter for get_airport_delays.
x402_paymentNoOptional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.
l402_credentialNoOptional L402 credential '<macaroon>:<preimage_hex>' (or 'L402 <macaroon>:<preimage>') from a paid invoice or an active subscription. Omit it to receive the Lightning invoice and macaroon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / x402_payment
      Added value: +{
      +  "description": "Optional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations only say readOnly and openWorld; the description goes far beyond by disclosing the cost (30 sats / $0.025 USDC), the exact failure path (HTTP 402 or MCP payment_required with invoice and macaroon), the two payment mechanisms with header names, and the settlement rule that only a 200 is settled. It also carries legal constraints ('Not for navigation', 'Not endorsed by the FAA or NOAA') that no annotation conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is correctly front-loaded in the first clause, but a long inline sample JSON and a dense payment paragraph bloat the text; the sample earns some place because there is no output schema, yet it is longer than needed to convey the response shape.

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 no output schema, the sample and field-level explanation are genuinely necessary and present, and the paid-call workflow is fully described end to end. The residual gap is the unresolved tension between 'airport required' in prose and zero required parameters in the schema, which could confuse an agent about the minimum valid call.

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 the schema already documents all six parameters, including the payment credentials and the airport aliases, so the baseline is 3. The description adds only the 'airport=SFO required' hint and otherwise repeats payment mechanics already spelled out in the l402_credential and x402_payment schema descriptions.

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+resource ('One US airport'), and enumerates the three payloads it returns: FAA delay/closure events, NOAA current weather, and NWS alerts. It is distinguishable from get_airport_delays by the extra weather/alert coverage, but it never states that differentiation explicitly, leaving the agent to infer it from the sibling name alone.

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?

Usage context is implied by the content description ('FAA delay/closure events plus... NOAA weather') and constrained by 'Not for navigation,' but there is no explicit when-to-use routing against get_airport_delays or the get_weather_* siblings. The parenthetical 'airport=SFO required' gives a concrete invocation hint, though it conflicts mildly with the schema's zero required parameters and its q/iata/icao aliases.

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