Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

Get the trip's menu

get_menu
Read-onlyIdempotent

Reads the candidate menu for one stop of a trip: real tours (bookable), sights, free ideas and food. Returns items with id, kind, rating, price and duration (a tour's runs_on lists the trip days it runs), plus a rules block to follow when picking. Reads only. While the menu is still arriving, the first result is a card that refreshes itself: do not call get_menu again for that stop (a repeat answers in text only). Use it to choose what goes on the days, then pass the chosen ids to place_picks; use get_trip to read the days already placed.

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": {
      "trip_id": "<trip_id>"
    },
    "name": "get_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly one kind: tour, sight, food or free.
limitNoRows per kind, best first (default 25, up to 120).
leg_idNoA stop's id (leg_id) on a multi-city trip, from start_trip's legs or get_trip's stops. Only this stop's menu. Default: a one-stop trip's whole menu; multi-city, the first stop without picks (the result lists the others).
trip_idYesThe trip's id (trip_id), as returned by start_trip or list_trips.
from_cardNoSet only by the menu card's own refresh; leave it out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), but the description adds non-obvious behavior: the menu streams in and the first result is a self-refreshing card, and a repeat call answers in text only. It also discloses the return shape (id, kind, rating, price, duration, runs_on, plus a rules block). Minor redundancy in restating 'Reads only', which annotations already 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?

Front-loaded with purpose, then return contents, then the streaming caveat, then routing to place_picks/get_trip. Dense but nearly every clause carries information; the parenthetical about runs_on is slightly cramped but earns its place.

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?

For a read tool with no output schema, the description fully covers what comes back, the async card behavior, and the downstream call. Nothing an agent needs to invoke it correctly 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 description coverage is 100%, so every parameter (kind enum, limit, leg_id default, trip_id, from_card) is already documented in the schema. The description reinforces the one-stop scoping of leg_id and explains runs_on, but adds little parameter-level detail the schema lacks. Baseline 3 is appropriate.

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+resource with scope ('Reads the candidate menu for one stop of a trip') and enumerates exactly what the menu contains (tours, sights, free ideas, food). This clearly separates it from siblings like get_trip (days already placed) and search_tours (standalone search).

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?

Gives explicit workflow guidance: 'Use it to choose what goes on the days, then pass the chosen ids to place_picks; use get_trip to read the days already placed.' It also names a when-not-to-call condition ('do not call get_menu again for that stop'), which is rare and valuable.

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