chucho — Book Direct

Find vacation homes

search_properties

Read-onlyIdempotent

Find vacation rentals, holiday homes and places to stay. Search immediately with free-text city, region or country and guest/pool/amenity needs; use get_filters only for ambiguous destinations or exact place/area keys. Shows photos and host booking buttons automatically. Returns approved facts, never rates or availability. Never ask for check-in/check-out dates, stay length or nightly budget; ignore offered dates/budget as filters and search the supported needs now.

Input Schema

TableJSON 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.
`locale`	No		en
`region`	No
`country`	No
`feature`	No	Collection key from the filter catalog.
`amenities`	No	Comma-separated amenity keys; every requested amenity must be explicitly present.
`minBedrooms`	No
`minBathrooms`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`total`	Yes
`locale`	Yes
`nextPage`	Yes
`pageSize`	Yes
`missingIds`	No
`properties`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields 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"
+}

changedOutput schema / properties / nextPage / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / page / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / page / minimum
```
Added value: +-9007199254740991
```

changedOutput schema / properties / page / type

Previous value: -"number"New value: +"integer"

addedOutput schema / properties / pageSize / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / pageSize / minimum
```
Added value: +-9007199254740991
```
changedOutput schema / properties / pageSize / type
```
Previous value: -"number"New value: +"integer"
```

addedOutput schema / properties / properties / items / properties / amenities

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / properties / items / properties / canonicalUrl
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / properties / items / properties / constraint
```
Added value: +{
+  "maxLength": 160,
+  "type": "string"
+}
```
addedOutput schema / properties / properties / items / properties / summary
```
Added value: +{
+  "maxLength": 240,
+  "type": "string"
+}
```

changedOutput schema / properties / properties / items / required

Previous value: -[
-  "id",
-  "name",
-  "place"
-]New value: +[
+  "id",
+  "name",
+  "place",
+  "amenities",
+  "canonicalUrl"
+]

addedOutput schema / properties / total / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / total / minimum
```
Added value: +-9007199254740991
```

changedOutput schema / properties / total / type

Previous value: -"number"New value: +"integer"

First observedOct 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: photos and host booking buttons render automatically, and results are limited to 'approved facts, never rates or availability,' which tells the agent what this tool will and won't return.

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 capability, then constraints and exclusions in tight sentences. Dense but nearly every clause carries actionable information; only the photos/booking-button sentence is marginal.

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?

With an output schema present, return-value detail is not required, and the description appropriately focuses on scope limits (no rates/availability) and input intent. Pagination via page and several filter params remain unaddressed, so it is not fully complete for a 14-parameter tool.

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 only 43% across 14 params, so the description must compensate. It clarifies the intended use of free-text q/city/region/country and guest/pool/amenity inputs, but says nothing about bounds, page, locale, feature, minBedrooms/minBathrooms or place-key semantics, leaving several parameters undocumented in both places.

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+resource ('Find vacation rentals, holiday homes and places to stay') and the primary input surface (free-text city/region/country plus guest/pool/amenity needs). It is clearly distinguishable from siblings like get_property (single lookup) and get_filters (catalog).

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?

Explicitly routes: 'Search immediately with free-text... use get_filters only for ambiguous destinations or exact place/area keys.' It also gives hard exclusions – never ask for dates, stay length or nightly budget, and ignore offered dates/budget as filters. This is unusually complete when/when-not guidance.

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?