Skip to main content
Glama
nanwer
by nanwer

list_active_watches

List active flight price watches, automatically re-check stale entries, and flag those where the price has dropped to or below the user's target.

Instructions

🎯 RENDERING DIRECTIVE — READ FIRST. When 2+ watches come back, render them as an HTML/React artifact — one card per watch with a clear "Cancel" button (callable via cancel_watch(watch_id)) and, for alerted watches, a "Book now" button to the flight booking URL. Alerted watches must be visually flagged (e.g. green badge or 🎯 callout). 1 watch may be prose.

List the user's active flight price watches. Re-runs any watch whose latest check is older than refresh_after_hours (default 6h) and flips status to "alerted" when the latest price is at or below the watch's threshold.

USE THIS TOOL WHEN: the user asks "any deals?", "what's the price of [route] looking like?", "show my watches", "anything trigger yet?", "did the Lisbon trip get cheaper?". Also use it proactively at the start of a session if you know the user has watches set up.

Returns a list of watch objects, each with:

  • watch_id, route (formatted "ORIGIN → DESTINATION"), departure_date, return_date

  • threshold_price, currency

  • status: "active" (no alert) or "alerted" (price hit threshold during refresh)

  • last_price / last_currency / last_offer_id: the latest observed price

  • last_checked_at: timestamp of the latest refresh

  • alerted_at: when the alert fired (null if not alerted)

  • note: the user's optional note from creation time

  • gap: numeric last_price - threshold_price (negative = below threshold, positive = above). Use this to summarize "X EUR below your target" or "still Y EUR above target".

Each refresh costs ONE fli call. Refresh frequency is bounded by refresh_after_hours — repeated calls within the cutoff window are free (no fli traffic). If you want a forced refresh, pass refresh_after_hours=0.

RESULT PRESENTATION: If any watch is alerted, lead with it (a small "🎯 Deal!" callout works well). For non-alerted watches, show the current gap ("currently 53 EUR above target, last checked 2h ago"). For never-checked watches, say so.

If include_cancelled=true, also include watches the user cancelled — useful when they ask "show me everything" or "what did I cancel last week?".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_cancelledNo
refresh_after_hoursNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully explains behavior: re-runs watches, flips status, costs one call per refresh, bounded by refresh_after_hours, forced refresh option. It also details return fields and side effects.

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?

The description is overly long with rendering directives and result presentation tips that could be separate. It is well-structured but not concise.

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?

The description covers all aspects: purpose, usage, parameters, behavior, return fields, and even rendering suggestions. It is complete given the lack of annotations and output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema coverage, the description explains both parameters: include_cancelled for listing cancelled watches, and refresh_after_hours for refresh frequency, including the forced refresh usage.

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 the tool lists active flight price watches, re-runs old checks, and flips status on threshold hits. It distinguishes itself from siblings like cancel_watch and watch_flight_price.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage examples are given: user queries like 'any deals?' or 'show my watches', and proactive use at session start. It provides clear context for when to invoke.

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/nanwer/trip-search-mcp'

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