Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

Rename or delete a trip

update_trip
DestructiveIdempotent

Renames, deletes or restores one of the traveller's own trips; one change per call. name renames it here and in the Adonde app. delete true moves it to the bin: it leaves list_trips and the app and its public link stops working, but nothing is erased, and restore true brings it back with its days and stops within 30 days. Returns what changed and how to undo it. Writes to the trip; another person's trip is refused. Ask before deleting. Use to tidy the traveller's trips; use list_trips to find a trip_id, share_trip to send a trip to others.

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": "update_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe new trip name, 1 to 80 characters, e.g. Lisbon with Ana. Renames the trip.
deleteNotrue moves the trip to the bin (deleted, restorable for 30 days). Only with the traveller's yes.
restoreNotrue brings a deleted trip back from the bin, within 30 days of the delete.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint/readOnlyHint=false, but the description adds what those hints cannot: deletion is a soft move to the bin, nothing is erased, the public link stops working, restore works within 30 days, and another person's trip is refused. It also discloses that the response includes undo instructions, which matters for a destructive tool.

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 the verb+resource and every sentence carries distinct information (semantics, safety, return, routing). It is a single dense run-on paragraph, though, which costs a little scannability.

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 destructive, no-output-schema mutation tool, the description covers the safety model, undo path, permission boundary, and return shape ('what changed and how to undo it'). No output schema exists, and the description compensates for that adequately.

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 still adds cross-cutting meaning the schema lacks, notably that name renames the trip 'here and in the Adonde app' and that delete/restore are mutually scoped to a 30-day window. It does not elaborate the intent_ref mechanics beyond the schema, keeping it just short of 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?

Opens with concrete verbs and the exact resource ('Renames, deletes or restores one of the traveller's own trips'), plus a scope constraint ('one change per call'). It also names the siblings it is not (list_trips, share_trip), so an agent can separate it from those 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?

Explicitly states when to use it ('to tidy the traveller's trips') and routes to alternatives: list_trips to find a trip_id, share_trip to send a trip. It also adds a procedural guard ('Ask before deleting') that an agent would otherwise not know to apply.

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