Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

Tour details

get_tour_details
Read-onlyIdempotent

Reads one tour in full. Returns photos, overview, what is and is not included, meeting point, pickup, duration, group size, languages, cancellation policy, accessibility and fitness notes, age bands, price per adult and child, rating and star breakdown (no review text) and the book_link; with date, whether it runs that day and its start times. Reads only; nothing is booked. Answer specific questions from its fields, naming the tour; if they do not say, say we do not know. Use for one tour from search_tours or the menu; use compare_tours for 2 to 4, search_tours to find tours, get_place_details for a sight or restaurant.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_tour_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoSame as product_code; send one of the two.
dateNoA day to check, YYYY-MM-DD: whether it runs, start times and that day's prices.
product_codeNoThe tour's product_code from search_tours, or a menu id like viator:12345P1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile, yet the description still adds real value: a full inventory of returned fields, an explicit limitation ("no review text"), date-dependent behaviour (whether it runs that day, start times, that day's prices), and the reassurance "nothing is booked". The only mild redundancy is restating the read-only nature already implied by readOnlyHint.

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?

Three dense sentences with the core action front-loaded, then the return inventory, then the routing alternatives. The long field enumeration is justified because there is no output schema, though it could be consolidated slightly without losing information.

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?

With no output schema, the description assumes responsibility for describing return content and does so exhaustively, including what is deliberately absent (review text) and how the optional date changes the result. Nothing an agent needs to call it or interpret its output is missing.

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% and already documents code/product_code aliasing and the YYYY-MM-DD date check. The description reinforces the date semantics via "with date, whether it runs that day and its start times", but adds no format or constraint detail beyond the schema, so baseline 3 applies.

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?

"Reads one tour in full" is a specific verb+resource with an explicit scope (one tour, full record), and the description immediately distinguishes it from compare_tours, search_tours and get_place_details. An agent can select it without opening the schema.

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?

Explicit routing: use this for one tour from search_tours or the menu, compare_tours for 2–4 tours, search_tours to find tours, get_place_details for sights/restaurants. It also states the answering convention (name the tour; say "we do not know" when fields don't say), which is when-to-use guidance at a behavioural level.

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

All Adónde 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