Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

Share a trip

share_trip
Destructive

Shares a built trip with other people. mode together emails each address an invitation to build the trip with the traveller (they join after signing in or up). mode show makes a read-only link anyone can open for 7 days, emailed to any addresses given and always returned so it can be copied. Returns a message and, for show, the link. Sends email, which cannot be unsent: share only with the traveller's yes and the addresses they gave; at most 10 emails a call, 20 per trip a day. revoke true switches off public links and invitations not yet accepted. Use to send a trip to others; use update_trip to rename or delete it, list_trips to find its trip_id.

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

Input Schema

NameRequiredDescriptionDefault
modeNotogether = invite to build it with the traveller; show = read-only link. Required to share; optional with revoke.
emailsNoUp to 10 addresses the traveller gave, e.g. ana@example.com. Required for together; optional for show.
revokeNoUndo sharing: switch off the trip's public links and withdraw invitations not yet accepted. Emails are not needed.
messageNoA short note shown in the email.
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.9/5.0
Behavior5/5

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

The annotations already mark this as destructive, non-read-only, non-idempotent, and open-world, but the description adds substantial behavior beyond that: emails cannot be unsent, invitations can be withdrawn if not accepted, public links last 7 days, and limits are 10 emails per call and 20 per trip per day. It also discloses what is returned.

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?

The description is dense but front-loaded: purpose first, then mode behavior, safety constraints, revoke behavior, and alternatives. Every sentence contributes operational or safety-relevant information for a destructive email-sending tool.

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?

Given six parameters, rich schema descriptions, annotations, and no output schema, the description is complete enough to call correctly. It explains the return shape at a high level and covers the destructive, email-sending, revocable nature of the operation.

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 schema already documents each parameter thoroughly, but the description adds operational meaning: together vs show mode effects, revoke behavior, and per-call/per-day email limits. It does not need to redefine every parameter because the schema already carries that burden.

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?

The description states a specific verb and resource: it shares a built trip with other people, and it distinguishes the two sharing modes. It also explicitly separates this tool from update_trip and list_trips, so an agent can identify its role among siblings.

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?

It gives direct usage guidance: use this to send a trip to others, use update_trip to rename or delete it, and list_trips to find the trip_id. It also states the consent prerequisite for sending email and the rate limits, which are critical when-to-use constraints.

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