Skip to main content
Glama

BreckenWander Travel

by com.breckenwander

Search experiences & activities on BreckenWander

search_experiences
Read-only

Search tours, activities, and experiences for a destination and get BreckenWander's all-in "from" price (USD). Returns a link that opens that specific experience to book on breckenwander.com. Read-only: does not book or take payment. Combine with flights and hotels into one trip using build_trip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adultsNoNumber of adults (context only; final price is set at booking).
date_toNoOptional end of a date range (YYYY-MM-DD).
childrenNoNumber of children.
date_fromNoOptional preferred date (YYYY-MM-DD); the exact date is chosen on breckenwander.com.
destinationYesCity or place name, e.g. "Rome" or "Cancun".
max_resultsNoHow many experiences to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
experiencesYes

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and the description reinforces with 'does not book or take payment.' It adds the behavior of returning a booking link and the 'from' price in USD, which goes beyond the safety hints.

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?

Four concise sentences covering purpose, price, link, read-only status, and integration with build_trip. No filler, all sentences earn their place.

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, the description does not need to enumerate return fields. It covers purpose, safety, output link, and integration, making it sufficiently complete for an agent.

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 covers 100% of parameters with descriptions; the tool description adds no parameter-specific details beyond the schema, so baseline 3.

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 specific verb 'Search' and resource 'tours, activities, and experiences' plus destination. It distinguishes from sibling tools (search_flights, search_hotels) by focusing on experiences and mentions integration with build_trip.

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?

Provides clear context: search experiences for a destination, returns a link, read-only not booking. It tells the agent to combine with build_trip for a full trip. However, it does not explicitly name alternatives like search_flights as alternatives; it only points to complementary use.

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

All BreckenWander Travel toolsInspect
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.5/5.0
Disambiguation5/5

Each tool addresses a distinct action: searching flights, hotels, experiences, and assembling a trip. There is no overlap in purpose.

Naming Consistency5/5

All tools use lowercase with underscores and a verb_noun pattern: search_flights, search_hotels, search_experiences, build_trip. The naming is uniform and predictable.

Tool Count5/5

With exactly 4 tools covering the core travel workflow (three searches and one assembler), the count is well-scoped and neither too sparse nor overly bulky.

Completeness5/5

The set covers the full journey from searching individual components to combining them into a bookable trip, with no obvious dead ends. Searches are read-only and direct booking links are provided, while build_trip handles combination.

Resources