Skip to main content
Glama

Update Event

update_event
Idempotent

Edit an existing event: fix its time, price, location, booking link or notes. Use when the user has new information about an activity that is already on the plan ("the tour starts at 10, not 9").

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

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.
eventKeyYesKey of the event on the variant, from 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. Changed1 schema field changed
    • addedInput schema / properties / data / properties / priceOptions
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "Alternative prices for this event when the group has a real choice, such as 4-day and 6-day ski passes. Use real prices only; leave this out when there is a single price. Prices are in the event's currency, so set currency too. Totals keep using totalCost. Replaces the whole list. Pass null to clear.",
      +      "items": {
      +        "properties": {
      +          "label": {
      +            "description": "What this price buys, e.g. \"6-day pass\".",
      +            "maxLength": 60,
      +            "type": "string"
      +          },
      +          "totalCost": {
      +            "description": "Total cost of this choice, in the event's currency.",
      +            "minimum": 0,
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "label",
      +          "totalCost"
      +        ],
      +        "type": "object"
      +      },
      +      "maxItems": 10,
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and idempotency profile is covered. The description adds only the implicit notion of an in-place correction of an existing event; it says nothing about partial-update semantics, whether other fields are preserved, or what comes back. That is useful but thin beyond the annotations.

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, front-loaded with the action and its scope, followed by the trigger condition and a short quoted example. There is no filler, and the example is the only elaboration, which is justified.

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 4-parameter, nested-object mutation tool with full schema coverage and a full annotation set, the description covers purpose and triggering context well. The remaining gap is that no output schema exists and the description does not indicate what the call returns or whether it echoes the updated event.

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 tripId, variantId, eventKey, and every nested field are already documented in the schema, including the 'omitted fields are left as they are' contract on `data`. The description's field list (time, price, location, booking link, notes) loosely mirrors schema properties but adds no format, precedence, or clearing guidance. Baseline 3 is appropriate.

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 gives a specific verb (edit) plus the resource (an existing event) and enumerates the editable facets: time, price, location, booking link, notes. That wording separates it cleanly from add_event, toggle_event, and delete_trip_item 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?

The second sentence gives an explicit trigger condition ('when the user has new information about an activity that is already on the plan') and reinforces it with a concrete example about a tour starting at 10 instead of 9. It does not name when-not cases or sibling alternatives such as add_event for new activities, which keeps it short of a 5.

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.