chucho — Book Direct

Your shortlist

open_shortlist

Read-onlyIdempotent

Open the conversation’s shortlist beside the chat. Saved public property IDs are kept in app model context and refreshed before display.

Input Schema

Name	Required	Description	Default
`q`	No	Search public property names, locations and approved introduction text.
`city`	No
`page`	No
`pool`	No
`place`	No	Place key from the live filter catalog.
`bounds`	No	Map viewport as south,west,north,east in degrees; keeps homes whose public area center is inside it. West greater than east crosses the antimeridian.
`guests`	No	Minimum sleeping capacity; required actual party size when requesting quote enrichment.
`locale`	No		en
`region`	No
`arrival`	No
`country`	No
`feature`	No	Collection key from the filter catalog.
`currency`	No
`amenities`	No	Comma-separated amenity keys; every requested amenity must be explicitly present.
`departure`	No
`quoteMode`	No	Optional price/availability enrichment. exact uses supplied dates and guests; estimate requires estimateWindowStart, estimateWindowEnd, estimateNights and guests for a clearly labeled sample within supplied flexible bounds. Search does not wait for every host or filter unknown homes out.
`relatedTo`	No	Published property ID. Find other homes from its organization, same locality first, then region/country and other locations. Excludes the source property. Additional filters still combine with AND.
`minBedrooms`	No
`minBathrooms`	No
`organization`	No	Exact organization slug returned on a property or in get_filters. Restricts results to that organization, across destinations.
`estimateNights`	No	Sample-stay nights, required. Only with quoteMode:estimate.
`estimateWindowEnd`	No	Latest sample departure (YYYY-MM-DD), paired with estimateWindowStart. Window must fit estimateNights (required), at most 150 days.
`estimateWindowStart`	No	Earliest sample arrival (YYYY-MM-DD), paired with estimateWindowEnd. Only with quoteMode:estimate. Preserve the traveler's flexible month or date range.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / currency / enum

Previous value: -[
-  "USD",
-  "EUR",
-  "GBP",
-  "CRC",
-  "MXN",
-  "COP",
-  "PEN",
-  "BRL"
-]New value: +[
+  "USD",
+  "EUR",
+  "GBP",
+  "CRC",
+  "MXN",
+  "COP",
+  "PEN",
+  "BRL",
+  "AUD"
+]

Changed5 schema fields changedOct 7, 2026

changedInput schema / properties / estimateNights / description

Previous value: -"Sample-stay nights, default 7. Only with quoteMode:estimate."New value: +"Sample-stay nights, required. Only with quoteMode:estimate."

addedInput schema / properties / estimateWindowEnd

Added value: +{
+  "description": "Latest sample departure (YYYY-MM-DD), paired with estimateWindowStart. Window must fit estimateNights (required), at most 150 days.",
+  "format": "date",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+  "type": "string"
+}

addedInput schema / properties / estimateWindowStart

Added value: +{
+  "description": "Earliest sample arrival (YYYY-MM-DD), paired with estimateWindowEnd. Only with quoteMode:estimate. Preserve the traveler's flexible month or date range.",
+  "format": "date",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+  "type": "string"
+}

changedInput schema / properties / guests / description

Previous value: -"Minimum sleeping capacity."New value: +"Minimum sleeping capacity; required actual party size when requesting quote enrichment."

changedInput schema / properties / quoteMode / description

Previous value: -"Optional price/availability enrichment. exact uses supplied dates and guests; estimate uses a clearly labeled future sample stay. Search does not wait for every host or filter unknown homes out."New value: +"Optional price/availability enrichment. exact uses supplied dates and guests; estimate requires estimateWindowStart, estimateWindowEnd, estimateNights and guests for a clearly labeled sample within supplied flexible bounds. Search does not wait for every host or filter unknown homes out."

Changed5 schema fields changedOct 7, 2026

addedInput schema / properties / arrival

Added value: +{
+  "format": "date",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+  "type": "string"
+}

addedInput schema / properties / currency

Added value: +{
+  "enum": [
+    "USD",
+    "EUR",
+    "GBP",
+    "CRC",
+    "MXN",
+    "COP",
+    "PEN",
+    "BRL"
+  ],
+  "type": "string"
+}

addedInput schema / properties / departure

Added value: +{
+  "format": "date",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+  "type": "string"
+}

addedInput schema / properties / estimateNights

Added value: +{
+  "description": "Sample-stay nights, default 7. Only with quoteMode:estimate.",
+  "maximum": 30,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / quoteMode

Added value: +{
+  "description": "Optional price/availability enrichment. exact uses supplied dates and guests; estimate uses a clearly labeled future sample stay. Search does not wait for every host or filter unknown homes out.",
+  "enum": [
+    "exact",
+    "estimate"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedOct 4, 2026

addedInput schema / properties / organization

Added value: +{
+  "default": "",
+  "description": "Exact organization slug returned on a property or in get_filters. Restricts results to that organization, across destinations.",
+  "maxLength": 160,
+  "type": "string"
+}

addedInput schema / properties / relatedTo

Added value: +{
+  "default": "",
+  "description": "Published property ID. Find other homes from its organization, same locality first, then region/country and other locations. Excludes the source property. Additional filters still combine with AND.",
+  "maxLength": 160,
+  "type": "string"
+}

Changed1 schema field changedOct 4, 2026

addedInput schema / properties / bounds

Added value: +{
+  "default": "",
+  "description": "Map viewport as south,west,north,east in degrees; keeps homes whose public area center is inside it. West greater than east crosses the antimeridian.",
+  "maxLength": 80,
+  "pattern": "^$|^-?\\d{1,3}(\\.\\d{1,6})?(,-?\\d{1,3}(\\.\\d{1,6})?){3}$",
+  "type": "string"
+}

AddedOct 3, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavior note — saved public IDs live in app model context and are refreshed before display — but says nothing about how the 23 filter parameters affect that refresh, pagination, or latency.

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?

Two sentences with no filler and the core action front-loaded, which is good. But for a tool exposing 23 parameters, this brevity reads as under-specification rather than discipline — nothing is wasted, yet too little is said.

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

Completeness2/5

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

This is a high-complexity tool: 23 parameters, five enums, no output schema, and a UI-side effect. The description explains only the display side effect and leaves the entire filtering surface, return behavior, and interaction with the shortlist unexplained, so an agent would not know how to call it correctly in practice.

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

Parameters2/5

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

Schema description coverage is only 52% across 23 parameters, which is below the threshold where the schema can carry the load alone. Parameters such as city, page, pool, region, country, locale, guests, arrival, departure, minBedrooms, minBathrooms and currency are undocumented in both schema and description, and the description adds no syntax, interaction, or default semantics to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ("Open the conversation's shortlist") and names the visible surface ("beside the chat"), so the basic action is clear. However, it does not reconcile the action with the 23 search/filter parameters the schema exposes, so an agent cannot tell whether this is a display action or a filtered query; the distinction from open_explorer/render_properties is left implicit.

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 when-to-use guidance and no exclusions. With siblings like open_explorer, render_properties, and search_properties, the description never says when opening the shortlist is preferred over rendering or searching, nor what preconditions (e.g. an existing saved shortlist) matter.

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.

Resources

Need Help?