BreckenWander Travel

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

Name	Required	Description
`adults`	No	Number of adults (context only; final price is set at booking).
`date_to`	No	Optional end of a date range (YYYY-MM-DD).
`children`	No	Number of children.
`date_from`	No	Optional preferred date (YYYY-MM-DD); the exact date is chosen on breckenwander.com.
`destination`	Yes	City or place name, e.g. "Rome" or "Cancun".
`max_results`	No	How many experiences to return.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`experiences`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "experiences": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "all_in_price": {
+            "type": "number"
+          },
+          "binding": {
+            "type": "boolean"
+          },
+          "captured_at": {
+            "type": "string"
+          },
+          "currency": {
+            "type": "string"
+          },
+          "disclosure": {
+            "type": "string"
+          },
+          "duration": {
+            "type": "string"
+          },
+          "duration_minutes": {
+            "type": "number"
+          },
+          "experience_id": {
+            "type": "string"
+          },
+          "guest_rating": {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          },
+          "image": {
+            "type": "string"
+          },
+          "location": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "price_basis": {
+            "type": "string"
+          },
+          "quote_expires_at": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "experiences"
+  ],
+  "type": "object"
+}

First observedJul 12, 2026

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 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.