Skip to main content
Glama

Find a cheaper stay

find_cheaper
Read-only

Given an Airbnb listing URL and trip dates, finds the same home bookable somewhere else (on HomeShared, where guests pay no service fee, or on a host's own booking site) and returns each match with its all-in total including fees and taxes, how confident the match is, a link, and when the price was checked, plus the savings against the Airbnb total for the same nights when that total is known (airbnb_total, or Airbnb's own prices for homes that copy them). Reads only that one public Airbnb listing page; it doesn't search Airbnb. If the home isn't listed anywhere else it returns no offers and says so.

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": {
      "airbnb_url": "<airbnb_url>",
      "check_in": "<check_in>",
      "check_out": "<check_out>",
      "adults": "<adults>"
    },
    "name": "find_cheaper"
  }
}

Input Schema

NameRequiredDescriptionDefault
petsNoPets (service animals don't count). Default 0
adultsYesGuests aged 13 or older
infantsNoGuests under 2; they don't count toward capacity. Default 0
check_inYesCheck-in date, YYYY-MM-DD
childrenNoGuests aged 2-12. Default 0
check_outYesCheck-out date (the morning the traveler leaves), YYYY-MM-DD
airbnb_urlYesThe Airbnb listing link, e.g. https://www.airbnb.com/rooms/12345678
airbnb_totalNoOptional: the total in USD that Airbnb shows at checkout for these dates and guests. Savings are measured against it when given. Without it, savings are reported only for homes whose prices are copied from their Airbnb calendar, against Airbnb's prices for the same nights

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / properties / airbnb_total / description
      Previous value: -"Optional: the total in USD that Airbnb shows at checkout for these dates and guests. Makes the savings exact instead of estimated"New value: +"Optional: the total in USD that Airbnb shows at checkout for these dates and guests. Savings are measured against it when given. Without it, savings are reported only for homes whose prices are copied from their Airbnb calendar, against Airbnb's prices for the same nights"
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond them: which external sources are consulted, that only one page is read, what each result contains (all-in total with fees and taxes, match confidence, link, price-check timestamp), how savings are computed and the airbnb_total fallback case, and the empty-result behavior.

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 core action and organized as action, return shape, then scope limits and edge case. It is a single dense paragraph with stacked parentheticals and a slightly tangled savings clause, but nearly every sentence carries useful information.

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?

There is no output schema, so the description carries the burden of explaining results, and it does: match contents, confidence, savings semantics, and the no-offers outcome. For a read-only, open-world lookup tool this is complete enough to call correctly.

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 description coverage is 100%, so every parameter including airbnb_total is already documented in the schema. The description restates the airbnb_total savings logic and the guest/date framing but adds no new syntax or constraint details, so the baseline 3 applies.

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: given an Airbnb listing URL and dates, it finds the same home bookable on other sites (HomeShared or a host's own site). It also pre-empts confusion with search_stays by explicitly saying it reads only that one public listing page and doesn't search Airbnb.

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

Usage Guidelines4/5

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

Gives clear preconditions (an Airbnb listing URL plus trip dates) and an explicit exclusion (it doesn't search Airbnb, so a searching tool is the alternative). It stops short of naming siblings like search_stays or get_quote directly, leaving the routing inference to the agent.

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