Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

Ask for trip details

open_trip_form
Read-onlyIdempotent

Shows a short trip details form (places, dates or month, length, party, budget, pace, flights, interests, notes), prefilled with what the traveller already said. Returns the form card; its Start button posts one line ending in a code, which start_trip takes as intent_ref. Creates nothing. Use when the traveller wants to plan a trip but details are missing, even before they name a destination; use start_trip directly when place, dates and party are known, suggest_route when they ask where to go. After the form is submitted, do not ask those questions again.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_trip_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
legsNoA multi-city route: the stops in order, with nights where known (suggest_route's stops).
knownNoEverything the traveller already said; the form starts with these values. Fields match start_trip's.
countryNoCountry name, e.g. Portugal. Send it when known; it keeps same-named cities apart.
destinationNoCity or town, e.g. Lisbon, if known.

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?

The annotations already declare readOnly, idempotent, non-destructive behavior, and the description adds important flow context: it returns a form card, its Start button posts a line ending in a code consumed by start_trip as intent_ref, and invoking it creates nothing. This makes the tool's side-effect profile and UI handoff clear.

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?

The description is front-loaded with the core action and return behavior, followed by routing guidance and a post-submission warning. It is efficient overall, though the parenthetical field list and workflow details make it denser than a minimal definition.

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-only form-opening tool with no output schema, the description explains what is returned (the form card), how the form hands off to start_trip, that nothing is created, and exactly when to use it versus alternatives. That is sufficient for an agent 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 description coverage is 100%, so the schema already documents the parameters in detail. The description lists the broad form fields (places, dates or month, length, party, budget, pace, flights, interests, notes) and says the form is prefilled, but it does not add parameter-level semantics beyond what the schema provides.

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 action and resource: it shows a prefilled trip details form, lists the form fields, says what it returns, and explicitly says it creates nothing. It also distinguishes the tool from siblings by naming start_trip and suggest_route with different conditions.

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 explicit use conditions and alternatives: use this when the traveller wants to plan but details are missing, even without a destination; use start_trip directly when place, dates and party are known; use suggest_route when they ask where to go. It also warns not to re-ask those questions after form submission.

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