Skip to main content
Glama

travel

by ai.autonomad
OverviewDiscussionsAdmin

search_activities

Read-onlyIdempotent

Searches tours, experiences and attractions from Viator in a city from a start date, with an optional end date and category (for example food tours, walking tours, museums or day trips). Results include name, category, duration, per-person price, rating and a photo; the response says whether these results can be booked. Searching does not reserve anything or charge anyone. If activities could not be checked, the result is { available: false, reason: "activities_unavailable", message } with no list: that does not mean "no activities" — pass on its message; flights, hotels and trips can still be searched and booked, and activities can be added after opening a booking link.

Input Schema

NameRequiredDescriptionDefault
cityYes
placeNoThe exact place of this trip stop: the `place` an earlier search for the trip returned, or the candidate the person picked when a search asked which place they meant. Searches given the same place cover the same place.
date_toNo
categoryNo
date_fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / place / properties / arrival_airports
      Added value: +{
+  "description": "The airports to fly this place by, best first, as a search returned them. Pass them back unchanged.",
+  "items": {
+    "properties": {
+      "iata": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "iata"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / place / properties / extent_km
      Added value: +{
+  "description": "The size of a region or island, as a search returned it.",
+  "type": "number"
+}
    • addedInput schema / properties / place / properties / gateway_airport
      Added value: +{
+  "description": "The one airport a wide search flies this place by, as a search returned it.",
+  "type": "string"
+}
    • addedInput schema / properties / place / properties / kind
      Added value: +{
+  "description": "What the place is, as a search returned it. Pass it back unchanged: a town, region or island has its hotels searched around it.",
+  "enum": [
+    "city",
+    "town",
+    "region",
+    "island"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / place / properties / radius_km
      Added value: +{
+  "description": "The hotel search radius for this place, as a search returned it.",
+  "type": "number"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / place
      Added value: +{
+  "description": "The exact place of this trip stop: the `place` an earlier search for the trip returned, or the candidate the person picked when a search asked which place they meant. Searches given the same place cover the same place.",
+  "properties": {
+    "airports": {
+      "description": "IATA codes of the airports serving the place.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "city": {
+      "type": "string"
+    },
+    "country": {
+      "description": "ISO 3166-1 alpha-2 code (territories use their own, e.g. PR).",
+      "type": "string"
+    },
+    "label": {
+      "description": "How to name the place to the person, e.g. 'Birmingham, GB'.",
+      "type": "string"
+    },
+    "latitude": {
+      "type": "number"
+    },
+    "longitude": {
+      "type": "number"
+    },
+    "region": {
+      "description": "State or region, or empty.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "country",
+    "latitude",
+    "longitude"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent), and the description goes well past them: it states that searching reserves nothing and charges no one, enumerates the return fields (name, category, duration, price, rating, photo) and a bookability flag, and specifies a distinct failure envelope { available: false, reason: "activities_unavailable", message } with no list, warning that this must not be read as zero activities.

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 action and resource in the first clause, then the return shape, then the failure semantics — a sensible order. It's a dense single paragraph with some run-on accumulation near the end, but each clause carries distinct information rather than filler.

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 no output schema, the description does the work of describing returns (fields, bookability flag) and the unavailability case, plus the follow-on path for adding activities. It omits result limits, pagination and date formatting, which are the remaining gaps for a search 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 20%, so the description must carry weight: it explains city, date_from/date_to (start date, optional end date) and category with concrete examples. However it never clarifies date formats or how the top-level 'city' relates to the richer 'place' object (both are accepted), leaving a real ambiguity for a 5-parameter tool.

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 and resource (searches Viator tours, experiences and attractions), plus scope constraints (a city, a start date) — an agent can distinguish it from search_events, search_dining and search_hotels without opening a schema. Category examples (food tours, walking tours, museums, day trips) further pin down the resource type.

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?

Gives clear conditions for use (city + start date, optional end date/category) and names the surrounding workflow alternatives by noting flights, hotels and trips can still be searched and booked when activities are unavailable. It stops short of explicitly declaring when NOT to pick this tool over its siblings, so it's clear context without true exclusions.

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

All travel toolsInspect
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