Skip to main content
Glama

Watch other whole homes for a booked stay's dates

watch_similar_homes
Idempotent

For a whole home already booked (watch_booking, then the first morning's read found the nights taken by the traveler): watches other verified whole homes nearby for the same dates and party, and emails the account when one comes in at least 5% or $50 under what they paid, until their free-cancellation deadline. A find is always a different home, never the same one cheaper; the traveler books the new one first and cancels theirs second. Starts with one live search now (30 to 90 seconds; not counted as a trip). Needs the key the booking was watched with; free.

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": {
      "bookedId": "<bookedId>"
    },
    "name": "watch_similar_homes"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookedIdYesThe bookedId watch_booking returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the trigger thresholds (5% or $50 under), the alert channel (email), the expiry (free-cancellation deadline), that the initial live search takes 30-90 seconds, that it isn't counted as a trip, that it requires the same key the booking was watched with, and that it costs nothing. It also rules out a misleading expectation by stating a find is never the same home cheaper.

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?

Front-loaded with the precondition and effect, and every clause carries information (threshold, timing, ordering, cost). It is a dense single block with heavy parenthetical nesting, which slightly hurts scanability but wastes no sentences.

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 one-parameter tool with no output schema, the description supplies everything an agent needs: the triggering condition, what the user will observe (email), how long the first call blocks, cost, and the follow-up action ordering.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3. The description adds real value by noting the tool 'needs the key the booking was watched with', clarifying that bookedId must come from the same credential context as the original watch — a constraint not captured in the schema.

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 ('watches other verified whole homes nearby for the same dates and party') plus the outcome (emails the account on a qualifying price drop). It is unambiguously distinct from watch_booking and set_alert, which are the nearest siblings.

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?

Gives an explicit precondition chain: the home must already be booked via watch_booking and the first morning's read must have found the nights taken. It also states the required workflow ordering — book the new home first, cancel the original second — so the agent knows not to advise cancellation upfront.

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