Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

Change a day

edit_day
DestructiveIdempotent

Changes one day of a trip using the item ids get_trip returns: remove items (remove_ids), move an item to another date or start time (move), or swap an item for another menu id (swap). Returns the updated days. Writes; a move or swap that does not fit is refused and the day is left exactly as it was. Bookings, stays, transport and blocked time are never changed; they are named back and left alone. Use for items already on the days; use add_stop to add one new item, place_picks to set whole days, build_trip to let our AI fill days.

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>",
      "day": "<day>"
    },
    "name": "edit_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesThe trip day being changed, YYYY-MM-DD.
moveNoItems on `day` to move to another date inside the trip.
swapNoItems on `day` to replace with another menu item at the same time.
trip_idYesThe trip's id (trip_id), as returned by start_trip or list_trips.
intent_refNoThe reference at the end of a chat line an Adonde card posted, e.g. K7Q2MD from "Code: K7Q2MD." (older cards: "(ref K7Q2MD)"). Pass it on its own: the card's exact arguments load on our side. Add only what the line says is still missing (for a route, the travellers).
remove_idsNoItem ids to remove, from get_trip's days[].items[].id.

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 flag destructiveHint=true and idempotentHint=true, and the description adds context beyond them: it discloses the write semantics, the atomic failure mode ("a move or swap that does not fit is refused and the day is left exactly as it was"), and a scope exclusion (bookings, stays, transport and blocked time are never changed and are named back). That last detail is important for an agent to know it cannot accidentally alter bookings.

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?

Four sentences, each carrying distinct information — scope, mechanics, failure behavior, alternatives — with the verb and operations front-loaded. Slightly dense with parenthetical parameter names, but nothing is wasted.

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 mutation tool with no output schema, the description states what returns ("Returns the updated days"), what fails and how, and what is out of scope. Combined with full schema coverage, an agent has everything needed to call it correctly.

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 every parameter including intent_ref is already documented in the schema. The description maps remove_ids, move and swap to their intent and ties ids back to get_trip, which is mildly useful, but it adds no format, limit or constraint detail beyond structured fields. 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?

Opens with a specific verb and resource ("Changes one day of a trip") and enumerates the three operations the tool supports: remove_ids, move, swap. An agent can distinguish this from add_stop, place_picks and build_trip immediately without inspecting schemas.

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?

Explicitly names the condition for this tool ("items already on the days") and routes to three named alternatives with their conditions: add_stop for one new item, place_picks for whole days, build_trip for AI-filled days. No inference required.

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