Skip to main content
Glama

Add Getting-Around Option

add_getting_around_option

Propose how the traveller moves around locally once at a destination — walking, public transport, rental car, bike, ride share. Use this for local mobility budgets; the journey between destinations belongs in add_transport_option.

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": {
      "tripId": "<tripId>",
      "variantId": "<variantId>",
      "destinationKey": "<destinationKey>",
      "data": "<data>"
    },
    "name": "add_getting_around_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe getting-around option to propose.
tripIdYesId of the trip, as returned by list_trips or get_trip.
variantIdYesId of the trip variant (an alternative version of the trip), from get_trip.
destinationKeyYesKey of the destination inside the variant, from get_trip (e.g. "destination-1").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / data / properties / type / description
      Added value: +"How the person will get around this place. Add one to every destination and select it: the app uses it for the travel time from each stay to the trip's events."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent local write, so the safety profile is covered. The description adds meaningful framing beyond that: the record is a *proposal* (not a committed choice), implying later selection via a select tool, which is real behavioral context. It does not say what happens on repeated calls for the same destination or whether an existing option is replaced, which is where the non-idempotent hint would benefit from elaboration.

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?

Two sentences, zero filler, with the core purpose front-loaded and the sibling disambiguation immediately after. Nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-required-parameter nested write with no output schema, the description covers purpose, scope and sibling boundaries adequately; the schema carries the field-level burden. The one minor gap is the return value — an agent doesn't learn whether the created option's id is returned for later use by select_destination_option.

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% and the nested data object documents type, cost, currency, link and notes thoroughly, including the enum semantics and the instruction to add one per destination. The description adds no parameter-level detail beyond that, so 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?

States a specific verb and resource — proposing how the traveller moves around locally at a destination — and enumerates the concrete modes (walking, public transport, rental car, bike, ride share). It distinguishes itself from siblings by explicitly naming add_transport_option as the tool for inter-destination journeys.

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?

Gives explicit when-to-use guidance ("Use this for local mobility budgets") and an explicit exclusion with the correct alternative ("the journey between destinations belongs in add_transport_option"). An agent can route between the two transport tools without opening either schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.