Skip to main content
Glama

Update Variant

update_variant
Idempotent

Rename a variant, change its dates (exact dates or a flexible window), edit its notes, or set who is travelling. Returns the variant as it now stands — read the response to confirm your change landed rather than assuming it did.

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

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.
variantIdYesId of the trip variant (an alternative version of the trip), from get_trip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / data / properties / participants / description
      Previous value: -"Who is travelling. Replaces the whole structure — send the full participant list, not just the part that changed."New value: +"Who is travelling. Replaces the whole structure — send the full participant list, not just the part that changed. Leaving out numberOfRooms erases it."
    • addedInput schema / properties / data / properties / participants / properties / children / items / properties / age / maximum
      Added value: +17
    • addedInput schema / properties / data / properties / participants / properties / children / items / properties / age / minimum
      Added value: +0
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, closed-world writes, so the safety profile is covered. The description adds genuinely new behavioral context that no structured field supplies: it returns the variant as it now stands, and it explicitly instructs the agent to read the response rather than assume success — important given there is no output schema. It stops short of 5 because it omits the destructive sub-behavior of the participants block (full replacement), which appears only in the schema.

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. The editable surface is front-loaded in the first sentence and the verification advice follows in the second. Every clause earns its place.

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?

With no output schema, the description correctly compensates by stating what is returned. Nested objects and the partial-update contract are handled by the rich schema. The one meaningful gap is that the whole-structure replacement of participants — the sharpest failure mode for this tool — is not surfaced in the description itself.

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 baseline is 3. The description restates the field groups (name, dates, notes, participants) and clarifies that dates may be either exact or a flexible window, which adds slight meaning to the anyOf structure, but it does not explain the participants-replacement semantics, date format expectations, or the roles of tripId/variantId beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (update) and enumerates the concrete editable facets: name, dates (exact or flexible window), notes, and participants. An agent immediately knows this mutates an existing variant. It does not distinguish itself from nearby siblings such as create_variant, duplicate_variant, or select_variant, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the verb — you call it when you want to change an existing variant — but the description never says when to use create_variant or duplicate_variant instead, nor does it mention prerequisites like having a variantId from get_trip. The partial-update rule ('omitted fields are left as they are') lives only in the schema, not the description.

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.