MCP Booking

booking_get_prices

Retrieve current room prices and the lowest available rate for a property by providing its URL, check-in, and check-out dates.

Instructions

Get current prices for a property for specific dates. Returns room options with pricing details and the lowest available price.

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": {
      "propertyUrl": "<propertyUrl>",
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>"
    },
    "name": "booking_get_prices"
  }
}

Input Schema

Name	Required	Description
`rooms`	No	Number of rooms (default: 1)
`adults`	No	Number of adults (default: 2)
`checkIn`	Yes	Check-in date in YYYY-MM-DD format
`checkOut`	Yes	Check-out date in YYYY-MM-DD format
`propertyUrl`	Yes	Full property URL or propertyId from search results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jun 25, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool returns pricing details and the lowest price, but does not mention idempotency, rate limits, authentication requirements, or any side effects. For a read operation, this is minimally adequate but lacks depth.

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?

The description is concise, consisting of two sentences that cover the core functionality. However, it could be structured more effectively (e.g., bullet points or a clear distinction between input and output).

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

Completeness3/5

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

Given the absence of an output schema, the description explains return values (room options, pricing details, lowest price). However, it lacks context about how to obtain the required 'propertyUrl', any prerequisites, or potential caveats like price volatility. It is functional but not fully comprehensive.

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 baseline score is 3. The description does not add significant extra meaning beyond what the schema already provides for each parameter; it essentially restates the purpose without elaborating on format, constraints, or relationships.

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?

The description clearly states the action ('Get current prices'), the resource ('a property'), and the constraints ('for specific dates'). It also specifies the return type ('room options with pricing details and lowest available price'). However, it does not explicitly differentiate from sibling tools like 'booking_check_availability', which might serve a similar purpose.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., requiring a propertyUrl from search results) or scenarios where this tool should not be used.

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

Deploy Server