Skip to main content
Glama
Sign In

Sparkflights

by io.github.Sparkflights-com
OverviewDiscussionsAdmin

watch_route

Idempotent

The Sparkflights page that saves a fare watch for a route: url opens the watch form with both cities and the cabin filled in. A watch covers every airport of both cities. Saving it needs a free Sparkflights account.

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

Input Schema

NameRequiredDescriptionDefault
cabinNoCabin to watch. Default economy.
originYesWhere the trip starts: an IATA airport code (JFK) for that airport, or a city for every airport the city's route pages cover: its name (New York), a metro code (NYC), or its name with its country or state (London, UK; Portland, Oregon)
destinationYesWhere the trip goes: an IATA airport code (NRT) for that airport, or a city for every airport the city's route pages cover: its name (Tokyo), a metro code (TYO), or its name with its country or state (London, UK; Portland, Maine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare a non-read-only but non-destructive, idempotent, closed-world operation, so the safety bar is partly met already. The description adds genuinely useful context the annotations cannot: the tool yields a URL to a form the user must open, a watch spans every airport of both cities, and account signup is required to save. It does not say whether any state changes server-side on call.

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 short sentences, front-loaded with the core action, and each adds a distinct fact (what it returns, the city-wide scope, the account requirement). The opening phrase 'The Sparkflights page that saves...' is slightly indirect about the tool's own behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small three-parameter tool with no output schema, the description covers what is returned (a URL), what that URL does, the scope of the watch, and the account prerequisite. Nothing an agent needs to decide to call it or to set expectations with a user is missing.

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%, including detailed origin/destination formats and the cabin enum with its default, so the schema carries parameter meaning. The description only adds that origin, destination, and cabin are pre-filled in the form, which is marginal confirmation rather than new semantics.

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?

Names a specific verb and resource (save a fare watch for a route) and clarifies that the tool returns a pre-filled watch-form URL rather than creating the watch itself. It implicitly separates itself from the deal-search siblings (get_deal/search_deals), though it never names them.

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 is only implied: an agent must infer that this is for monitoring a route's fares rather than fetching current deals. The one explicit gating fact is the prerequisite that saving requires a free Sparkflights account, and there is no statement of when not to use it or which sibling to prefer.

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

All Sparkflights toolsInspect
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