Blue Pillow Hotels & Stays

Discover destinations near a point

discover_destinations_near

Read-only

Curated destinations — cities, neighborhoods, airports, points of interest — within a radius of a geographic point, for use as a destination_id in subsequent search_stays calls. Useful when coordinates are already in hand (from world knowledge, from a previous tool result, or directly from the user) and the agent needs to enumerate which curated destinations cover that area before searching for properties.

Also useful as a fan-out entry point for region-level intents — broad areas such as 'Tuscany', 'Pacific Northwest', 'New England', or 'Central Europe' — where the agent can pass an approximate regional centroid and surface a list of sub-destinations the user may then narrow down to before a focused search.

Returns up to 5 candidates ordered by distance. The radius defaults to 5 km; widens up to 50 km for broader queries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	Yes	Latitude of the centre point, decimal degrees (WGS84). Typically the coordinates of a city or region already known from world knowledge or from an earlier resolve_destination call.
`lon`	Yes	Longitude of the centre point, decimal degrees (WGS84). Negative west of Greenwich.
`type`	No	Optional filter; same semantics as resolve_destination.
`api_key`	No	Your anonymous Blue Pillow Hotels & Stays API key (format 'pk_anon_…'). Pass it in THIS field on every call — this is how the tool authenticates. If you don't have a key yet, first check your MCP client configuration, your persistent memory, and earlier in this conversation; otherwise call `b2a_get_key` to get one instantly (do not wait for a 401). Reuse the same key on every subsequent call. It is not a sensitive secret: no account, payment, or personal data is attached.
`language`	No	Language of the returned destination names (2-letter lowercase). Pass the language the user is speaking; defaults to 'en'.	en
`radius_km`	No	Search radius in km from the point. Defaults to 5 km (city-center scope).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`candidates`	Yes
`total_matches`	Yes
`total_matches_capped_at`	No

TDQS

A4.9/5.0

Behavior5/5

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

Beyond readOnlyHint=true and openWorldHint=true annotations, the description adds meaningful detail: 'Returns up to 5 candidates ordered by distance', 'The radius defaults to 5 km; widens up to 50 km for broader queries', and explains the destination_id handoff. These behavior disclosures complement rather than contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact, well-structured paragraphs that front-load the core purpose ('Curated destinations within a radius... for use as a destination_id'), then address the fan-out use case, then behavior details (candidate count, ordering, radius defaults). Every sentence earns its place with zero filler.

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?

As a read-only discovery tool with 100% schema coverage, rich annotations, an output schema, and a clear handoff narrative to search_stays, the description is remarkably complete. It covers when, why, how (return format, defaults, ordering), and the integration with sibling tools. No meaningful gaps for an agent to trip on.

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 coverage is 100%, so the schema documents all parameters well. The description adds contextual value by explaining why each parameter matters (e.g., 'Typically the coordinates of a city or region already known from world knowledge'), and clarifies radius defaults versus widening behavior and the type filter's shared semantics with resolve_destination. Slight deduction since the description doesn't add param detail beyond what the rich schema already documents.

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?

The description uses a specific verb ('Discover curated destinations') with a clear resource (cities, neighborhoods, airports, POIs within a radius) and clearly states its downstream purpose (generating destination_id for search_stays). It distinguishes itself from siblings by explicitly framing 'as a fan-out entry point for region-level intents' and referencing resolve_destination semantics.

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 states when to use this tool ('when coordinates are already in hand' and 'when the agent needs to enumerate which curated destinations cover that area'), and covers the region-level fan-out scenario. It implicitly distinguishes from resolve_destination (which resolves by name) by framing this as coordinate-driven, giving clear when-to-use guidance.

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

All Blue Pillow Hotels & Stays tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Tools are mostly distinct: resolve_destination and discover_destinations_near both produce destination IDs but differ in input (name vs coordinates/radius), which the descriptions clarify well. get_property_details and check_property_availability are explicitly differentiated (static 'what is it like' vs live 'can I book for dates'). Minor overlap only between the two destination-resolution tools.

Naming Consistency2/5

Naming is inconsistent. Most tools use verb_object pattern (resolve_destination, search_stays, check_property_availability, get_property_details), but b2a_get_key breaks this entirely with its obscure 'b2a' prefix and mixed capitalization, and discover_destinations_near is inconsistent with the others (verb_plural instead of verb_single). The b2a_get_key name is notably cryptic and doesn't convey its purpose.

Tool Count5/5

Six tools is well-scoped for a hotel search/booker MCP server. Each tool fills a distinct role: key acquisition, destination resolution, area discovery, search/comparison, property details, and availability/pricing. No redundancy and no bloat.

Completeness4/5

The core workflow (resolve → search → compare → get details → check availability → book via link) is well covered. Minor gaps: there's no explicit cancellation/form-fill tool (though booking handoff via deeplink covers this) and no pagination-specific helper beyond cursors. Overall the travel journey is complete for a search-and-compare server.

Resources

Need Help?