chucho — Book Direct

Discover public filters

get_filters

Read-onlyIdempotent

Discover supported destination keys and filter counts. Use kind:geography to browse continents/subregions, their parent keys, available ISO country codes and counts; use exact geographicArea keys or countries codes in search. Use q with a host's name to find its organization slug (up to 20 name matches on the first page; refine q when more may exist), and organization to scope coverage to that exact slug; other calls return no organizations. Defaults to countries. Use q for a destination name, country to scope coverage, place for child destinations, and page until nextPage is null. Unneeded for city/country text searches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_filters"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No	Public destination or host organization name to look up; searches labels and organization names, not property descriptions.
`kind`	No	Destination level. geography returns the supported geographic hierarchy, available ISO country codes and counts; use its exact keys in search geographicArea. Without a query or scope, lists countries.
`page`	No
`place`	No	Exact place key to list its immediate children.
`locale`	No		en
`country`	No	Country name or ISO code to scope counts.
`organization`	No	Exact organization slug returned on a property or in get_filters. Restricts results to that organization, across destinations.
`geographicArea`	No	Exact geographic area key from get_filters(kind:geography), including continents and subregions. Americas includes North/Central/South America and the Caribbean. north-america includes Northern America, Central America and Caribbean; northern-america is the narrower UN M49 subregion. Filters by public ISO country/territory code; unknown locations never match. Combines with all other filters using AND.

Output Schema

Name	Required	Description	Default
`page`	Yes
`pool`	Yes
`total`	Yes
`places`	Yes
`features`	Yes
`nextPage`	Yes
`pageSize`	Yes
`amenities`	Yes
`totalPlaces`	Yes
`organizations`	Yes
`geographicAreas`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / q / description

Previous value: -"Public destination name to look up; searches labels, not property descriptions."New value: +"Public destination or host organization name to look up; searches labels and organization names, not property descriptions."

First observedOct 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavior: q returns up to 20 organization-name matches on the first page, organization scopes coverage to an exact slug, and other calls return no organizations. It also explains pagination and exact-key matching behavior including that unknown locations never match.

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 front-loaded with purpose and then covers usage modes, with no clearly wasted sentences. However, it is a dense run-on paragraph with semicolons and some repetition, making it less scannable than it could be for an 8-parameter tool.

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?

Given the output schema and read-only annotations, the description provides enough behavioral and usage context to invoke the tool correctly. It covers discovery, scoping, hierarchy keys, organization lookup limits, pagination, and when not to use the tool.

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

Parameters4/5

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

Schema description coverage is already 75%, so the baseline is 3. The description adds useful semantics for q, kind, place, country, organization, geographicArea, and pagination, though it does not mention locale, leaving one minor parameter unexplained beyond the schema.

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 that this tool discovers supported destination keys and filter counts, which is a specific verb/resource pair. It also distinguishes itself from text search by saying it is "unneeded for city/country text searches," though it does not explicitly name the sibling search tool.

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?

It gives detailed when-to-use guidance for each mode: kind:geography for hierarchy browsing, q for destination or host organization lookup, organization to scope to a slug, and page until nextPage is null. It also states when the tool is not needed, namely for city/country text searches.

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.