chucho — Book Direct

Get host booking link

get_booking_link

Read-onlyIdempotent

Get a currently published property's host destination, reviewed bookingCapabilities and matching handoff instructions. Request-only homes accept a booking request; price-only readers cannot confirm availability. Unknown or expired capabilities never promise online quotes or checkout. Open the destination for the host's booking options. This tool never creates a reservation or takes payment. Set includeCapabilities:true to inspect the current host capability. bookingStatus=requires_host_confirmation describes Chucho's handoff, not proof of manual host approval. A quote capability does not establish instant booking; say when the host's confirmation method is unknown.

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": {
      "id": "<id>"
    },
    "name": "get_booking_link"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`locale`	No		en
`currency`	No	Preferred ISO 4217 currency, e.g. USD, EUR or NOK. Rough nightly estimates use approximate conversions (USD by default) when a fresh rate is supported; otherwise retain the host currency. Dated quotes depend on host support: always inspect the returned currency. May be supplied without dates for browsing.
`includeCapabilities`	No	Set true to include the current host bookingCapabilities. Use for questions about booking methods, price checks or host approval. Missing or expired evidence remains unknown.

Output Schema

Name	Required	Description	Default
`action`	Yes
`bookingUrl`	Yes
`propertyId`	Yes
`instructions`	Yes
`propertyName`	Yes
`bookingStatus`	Yes
`bookingProvider`	Yes
`reservationCreated`	Yes
`bookingCapabilities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / currency

Added value: +{
+  "description": "Preferred ISO 4217 currency, e.g. USD, EUR or NOK. Rough nightly estimates use approximate conversions (USD by default) when a fresh rate is supported; otherwise retain the host currency. Dated quotes depend on host support: always inspect the returned currency. May be supplied without dates for browsing.",
+  "pattern": "^[A-Z]{3}$",
+  "type": "string"
+}

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / includeCapabilities

Added value: +{
+  "const": true,
+  "description": "Set true to include the current host bookingCapabilities. Use for questions about booking methods, price checks or host approval. Missing or expired evidence remains unknown.",
+  "type": "boolean"
+}

First observedOct 22, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses real behavioral nuance: no reservation or payment is ever created, unknown or expired capabilities must not promise quotes or checkout, bookingStatus=requires_host_confirmation is Chucho's handoff rather than host approval, and a quote capability does not imply instant booking. These are non-obvious constraints an agent could easily get wrong.

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 purpose is front-loaded and each caveat is individually relevant, but the capability caveats are restated across several sentences ('Unknown or expired capabilities never promise online quotes or checkout', 'A quote capability does not establish instant booking', 'say when the host's confirmation method is unknown'), which reads as dense and repetitive rather than tight.

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?

An output schema exists, so return values need not be explained, and the description thoroughly covers the dangerous misinterpretations of capability and status data. The main remaining gap is lack of guidance on the 'id' and 'locale' parameters and on how this differs from get_stay_quote.

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 coverage is 50%, and the two documented parameters (currency, includeCapabilities) already carry explanations in the schema. The description reinforces includeCapabilities:true in prose but says nothing about 'id' or 'locale', so it does not compensate for the coverage gap.

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 opening sentence gives a specific verb ('Get') and enumerates the resources returned: host destination, reviewed bookingCapabilities, and handoff instructions. It is distinguishable from get_property, but it never names the nearest siblings (get_stay_quote, get_stay_estimate) that an agent would weigh it against.

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?

It gives clear usage conditions: request-only homes accept a booking request, price-only readers cannot confirm availability, and 'Open the destination for the host's booking options.' It also states exclusions ('never creates a reservation or takes payment'), but it never explicitly routes to an alternative tool for quotes or estimates.

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

All chucho — Book Direct tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.