Skip to main content
Glama

Add a watched route

add_watch

Monitor a flight or train route by adding it to a watchlist; get an immediate fare check with resolved provider codes and continue receiving hourly updates on new offers.

Instructions

Add a route to monitor. originQuery/destinationQuery go through the same resolution as resolve_location for every requested provider, immediately, and the watch stores each provider’s resolved codes — you get that resolution back in the response so you can sanity-check it before relying on the watch. An immediate first check runs right away (you do not have to wait for the hourly cycle to get initial results) and its offers are returned too.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoFree-text label to help you recognize this watch later
dateToYesYYYY-MM-DD
currencyNoPreferred currency code for providers that support choosing one (Kupibilet, SpiceJet). Providers ignore this if they don’t support it and return their own default currency instead — always read the currency field on each offer.
dateFromYesYYYY-MM-DD
maxPriceNoIgnore offers above this price (in each provider’s own currency)
providersNoProvider ids to search; defaults to providers that work without a browser session (currently ryanair, kupibilet, spicejet). Pass ["jetstar"] explicitly to try it anyway.
originQueryYese.g. "Москва" / "Moscow" / "MOW"
destinationQueryYese.g. "Таиланд" / "Thailand" / "BKK"
Behavior4/5

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

With no annotations, the description fully explains behavioral traits: immediate resolution of locations, storage of codes, and an immediate first check returning offers. It lacks details on idempotency or duplicates but is otherwise transparent.

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?

Three sentences, front-loaded with the core purpose, and efficiently explains complex behavior without redundancy. Every sentence adds value.

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?

Given 8 parameters and no output schema, the description covers resolution, immediate check, and response contents. It could mention duplicate handling or resource limits but is largely complete.

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?

The schema provides 100% coverage with detailed descriptions. The tool description adds context about resolution and immediate check but does not significantly enhance per-parameter semantics. Baseline 3 is appropriate.

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?

The description clearly states 'Add a route to monitor' and explains the watch's purpose, distinguishing it from sibling tools like list_watches or remove_watch.

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?

The description explains what the tool does but does not explicitly state when to use it versus alternatives like force_check or poll_new_offers. The context is implied but not clearly demarcated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bitwiresys/air-choose'

If you have feedback or need assistance with the MCP directory API, please join our Discord server