Skip to main content
Glama

Buscar actividades

search_activities
Read-onlyIdempotent

Search tours and activities on WizTrip (Hotelbeds activities) in a city, between from and to (up to 60 days from tomorrow), for travellers of the given ages (every traveller, adults included). Prices are WizTrip selling prices in USD for the whole group, "from". Activities are not sold alone on wiz-trip.com: they are added when booking a flight, hotel or trip there (or ask Wizzo with trip_chat to add one to the trip).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>",
      "ages": "<ages>"
    },
    "name": "search_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesYYYY-MM-DD, from today (2026-11-19) on.
agesYesAge of every traveller, e.g. [35, 33, 8].
cityNoCity name, e.g. "Río de Janeiro".
fromYesYYYY-MM-DD, from today (2026-11-19) on.
iataNoIATA city code, if known.
textNoOptional keyword, e.g. "Cristo Redentor".
country_codeNoISO-2 country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-18) on."New value: +"YYYY-MM-DD, from today (2026-11-19) on."
    • changedInput schema / properties / to / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-18) on."New value: +"YYYY-MM-DD, from today (2026-11-19) on."
  2. Changed2 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-17) on."New value: +"YYYY-MM-DD, from today (2026-11-18) on."
    • changedInput schema / properties / to / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-17) on."New value: +"YYYY-MM-DD, from today (2026-11-18) on."
  3. Changed2 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-16) on."New value: +"YYYY-MM-DD, from today (2026-11-17) on."
    • changedInput schema / properties / to / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-16) on."New value: +"YYYY-MM-DD, from today (2026-11-17) on."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds substantive traits: a 60-day-from-tomorrow booking window, whole-group USD selling prices with 'from' semantics, and the constraint that activities cannot be booked in isolation — none of which the annotations convey.

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?

Two sentences, front-loaded with the core action and scope, with the constraint and booking-path caveat following. Slightly dense with parenthetical asides ('Hotelbeds activities', 'or ask Wizzo with trip_chat'), but nothing is redundant.

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?

For a seven-parameter, read-only search with no output schema, the definition covers scope, time window, pricing basis, and the downstream booking constraint. It omits any hint of result shape or result limits, which is a minor gap given no output schema exists to carry that.

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 coverage is 100%, so all seven parameters are already documented, making 3 the baseline. The description does add a little meaning — that `ages` covers every traveller including adults and that the window is capped at 60 days — but it does not clarify the interplay of `city`/`iata`/`country_code` or `text` beyond the schema.

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 ('Search tours and activities on WizTrip') plus the upstream supplier (Hotelbeds), scoping it to a city and a date range. This clearly separates it from the flight/hotel/transfer search siblings without needing to name them.

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 real context on when this is relevant: activities are not sold standalone on wiz-trip.com, only attached to a flight/hotel/trip booking, and it names `trip_chat` as the route to add one. It does not state explicit when-not conditions for the search itself, but the practical usage framing is stronger than typical.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources