Skip to main content
Glama

Update Trip

update_trip
Idempotent

Change top-level trip fields: rename it, set a cover photo, set the owner's budget, or move it through its lifecycle (planning -> ready once the plan is settled, finished or cancelled afterwards). Does not touch variants, destinations or options. Setting status to finished or cancelled frees the free plan's one active trip, so the user can start another; moving a finished or cancelled trip back to planning or ready is refused with 403 on the free plan while another trip is active.

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

Input Schema

NameRequiredDescriptionDefault
dataNoFields to change. Omitted fields are left as they are.
tripIdYesId of the trip, as returned by list_trips or get_trip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / data / properties / budget
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "What the owner wants to spend. Only the trip owner can change it. Set it only when the owner has stated one; without it, no budget warnings appear. Pass null to clear.",
      +      "properties": {
      +        "amount": {
      +          "description": "The most the owner wants to spend, as a positive number.",
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "appliesTo": {
      +          "description": "\"stay\" compares the budget with the accommodation cost alone, \"total\" with the whole trip.",
      +          "enum": [
      +            "stay",
      +            "total"
      +          ],
      +          "type": "string"
      +        },
      +        "currency": {
      +          "description": "Three-letter currency code (e.g. \"EUR\").",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "amount",
      +        "currency",
      +        "appliesTo"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing a real consequence: setting status to finished or cancelled frees the free plan's single active trip slot, and reverting a terminal trip to planning/ready is refused with 403 while another trip is active. This is exactly the kind of side effect and failure mode an agent cannot get from readOnlyHint/destructiveHint/idempotentHint.

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 affected fields and exclusions before the longer free-plan caveat; every clause carries information. The lifecycle sentence is long and slightly nested, but trimming it would lose the 403 precondition.

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 nested-payload mutation tool with no output schema, it covers affected fields, exclusions, owner-only constraints, and a concrete error condition. Nothing an agent needs to call it correctly is missing.

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 baseline is 3; the description still adds value by linking 'status' to concrete lifecycle transitions and clarifying that omitted fields are preserved and that renames are top-level only. It adds less on budget/coverPhoto, whose semantics live almost entirely in the schema.

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 plus the exact resource surface it mutates (name, cover photo, budget, status) and explicitly scopes out variants, destinations and options. An agent can distinguish it from update_variant/update_destination/update_destination_option without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-to-use guidance through the lifecycle rules (planning -> ready once the plan is settled; finished/cancelled afterwards) and negative scoping ('Does not touch variants, destinations or options'). It does not name the sibling tool to use for those excluded operations, so routing is implied rather than explicit.

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.