Adónde

Add one thing to a day

add_stop

Adds one menu item to one day through the same placing code as place_picks, keeping the items already on that date. Give a menu id from get_menu, or a name that clearly matches one menu item; start is an optional time hint (tours keep their real departures). Returns the updated day. Writes; when the name matches no item or several, or the item cannot fit, nothing is added and the error says why. Use for a single addition; use place_picks to set whole days, edit_day to remove, move or swap placed items.

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>",
      "date": "<date>"
    },
    "name": "add_stop"
  }
}

Input Schema

Name	Required	Description
`id`	No	A menu item id from get_menu, e.g. viator:12345P1 or osm:node/123.
`date`	Yes	The trip day to add to, YYYY-MM-DD.
`name`	No	The item's name, used when no id is given; must match one menu item clearly.
`start`	No	Start time hint, 24 hour HH:MM; our packer may shift it to fit. Ignored for tours.
`trip_id`	Yes	The trip's id (trip_id), as returned by start_trip or list_trips.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations: it states that existing items are kept, that ambiguity or fit failure results in no addition with an explanatory error (atomic failure semantics), and that 'start' is only a hint the packer may shift while tour departures stay fixed. That is the kind of context destructiveHint/idempotentHint cannot convey.

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?

Five compact sentences, front-loaded with what the tool does, then inputs, then failure behavior, then routing. Implementation-flavored phrase 'same placing code as place_picks' still earns its place by signaling behavioral parity.

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?

No output schema exists, so the description supplies the return value ('Returns the updated day'). For a non-destructive, non-idempotent write with 5 params, the description covers inputs, write semantics, failure modes, and alternatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds real value by framing id and name as alternatives ('a menu id from get_menu, or a name that clearly matches one menu item') and clarifying that start is a hint. The tour-ignores-start rule duplicates the schema, keeping it from a 5.

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 ('Adds one menu item to one day') and immediately anchors it to the sibling it shares code with (place_picks). An agent can distinguish it from place_picks and edit_day without opening a 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 for a single addition; use place_picks to set whole days, edit_day to remove, move or swap placed items.' Both the positive case and the alternatives are named with the condition that selects each.

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

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

Resources

Need Help?