Skip to main content
Glama

Change an activity

update_activity

Changes an activity’s details: only the fields given change, and null clears one. To move it to another day or lane, or reorder a day, use move_activity. Someone else’s change made meanwhile is kept, unless it was to the same field. Surprises kept from the user can’t be changed.

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

Input Schema

NameRequiredDescriptionDefault
dateNo
iconNo
typeNo
notesNo
placeNo
titleNo
tripIdYesThe trip’s id, from list_trips
endDateNo
endTimeNo
endPlaceNo
timeZoneNo
startTimeNo
activityIdYes
endTimeZoneNo
placeProviderIdNoA place’s providerId, from search_places
endPlaceProviderIdNoWhere a flight or transport arrives: a place’s providerId, from search_places

Output Schema

NameRequiredDescriptionDefault
activityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / icon
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "Its art from the app’s library, only when asked for: the app picks art by what it is (a sushi place gets sushi)",
      +      "enum": [
      +        "ramen",
      +        "sushi",
      +        "cafe",
      +        "museum",
      +        "temple",
      +        "beach",
      +        "onsen",
      +        "go-kart",
      +        "hotel",
      +        "pizza",
      +        "burger",
      +        "curry",
      +        "dim-sum",
      +        "tacos",
      +        "pasta",
      +        "steak",
      +        "pad-thai",
      +        "korean-bbq",
      +        "bakery",
      +        "dessert",
      +        "ice-cream",
      +        "street-food",
      +        "seafood",
      +        "breakfast",
      +        "vegan",
      +        "kebab",
      +        "restaurant",
      +        "cocktail-bar",
      +        "pub",
      +        "wine",
      +        "bubble-tea",
      +        "tea-house",
      +        "juice-bar",
      +        "nightclub",
      +        "karaoke",
      +        "rooftop-bar",
      +        "castle",
      +        "tower",
      +        "bridge",
      +        "palace",
      +        "monument",
      +        "viewpoint",
      +        "church",
      +        "mosque",
      +        "ruins",
      +        "art-gallery",
      +        "aquarium",
      +        "ferris-wheel",
      +        "lighthouse",
      +        "buddha-statue",
      +        "shrine",
      +        "old-town",
      +        "market",
      +        "theatre",
      +        "mountain",
      +        "waterfall",
      +        "park",
      +        "lake",
      +        "forest",
      +        "island",
      +        "garden",
      +        "volcano",
      +        "cave",
      +        "glacier",
      +        "river",
      +        "canyon",
      +        "vineyard",
      +        "farm",
      +        "flower-field",
      +        "desert",
      +        "cliffs",
      +        "national-park",
      +        "hiking",
      +        "skiing",
      +        "diving",
      +        "surfing",
      +        "theme-park",
      +        "zoo",
      +        "concert",
      +        "cinema",
      +        "cycling",
      +        "kayak",
      +        "boat-tour",
      +        "water-park",
      +        "golf",
      +        "stadium",
      +        "massage",
      +        "fitness",
      +        "bowling",
      +        "escape-room",
      +        "synagogue",
      +        "swimming-pool",
      +        "climbing",
      +        "horse-riding",
      +        "picnic",
      +        "arcade",
      +        "fishing",
      +        "ice-rink",
      +        "playground",
      +        "mall",
      +        "shopping",
      +        "souvenir",
      +        "fashion",
      +        "bookstore",
      +        "supermarket",
      +        "electronics",
      +        "cosmetics",
      +        "toys",
      +        "airport",
      +        "train",
      +        "ferry",
      +        "car",
      +        "bus",
      +        "bike-share",
      +        "taxi",
      +        "metro",
      +        "cable-car",
      +        "camping",
      +        "villa",
      +        "cabin",
      +        "resort",
      +        "apartment",
      +        "guesthouse",
      +        "hostel",
      +        "campervan",
      +        "home"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / activity / properties / attachments
      Added value: +{
      +  "description": "Its tickets and files, oldest first, to open in the app; none for a surprise kept from you",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "size": {
      +        "description": "In bytes",
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      "type": {
      +        "description": "Its media type: application/pdf, image/jpeg, image/png or image/webp",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "type",
      +      "size"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / activity / properties / icon
      Added value: +{
      +  "description": "The art someone picked for it, from the app’s library; null while the app picks it by what it is",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / activity / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "type",
      -  "date",
      -  "endDate",
      -  "startTime",
      -  "endTime",
      -  "timeZone",
      -  "place",
      -  "endPlace",
      -  "endTimeZone",
      -  "notes",
      -  "laneId",
      -  "surprise"
      -]New value: +[
      +  "id",
      +  "title",
      +  "type",
      +  "date",
      +  "endDate",
      +  "startTime",
      +  "endTime",
      +  "timeZone",
      +  "place",
      +  "endPlace",
      +  "endTimeZone",
      +  "notes",
      +  "laneId",
      +  "surprise",
      +  "icon",
      +  "attachments"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, destructive=false, closed-world), while the description adds genuinely new behavior: partial-patch semantics, null-to-clear semantics, field-level conflict resolution against concurrent edits, and an access restriction ("Surprises kept from the user can't be changed"). None of that is derivable from the annotations or schema, and none of it contradicts the hints.

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?

Four dense sentences, front-loaded with the mutation semantics before the sibling routing, with no filler. The closing line about surprises is terse to the point of being cryptic, but it is short rather than padded.

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 16-parameter partial-update mutation, the description covers the failure modes that matter (accidental overwrite, null handling, concurrent edits, forbidden targets), and an output schema exists so return values need no prose. The remaining gap is per-field guidance for a schema that documents only a fifth of its properties.

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 coverage is only 19% across 16 parameters, so the description carries a larger burden; it compensates partly by stating the null-clears-a-field rule, which applies uniformly to the many nullable fields. However, it names no individual field (type, icon, timeZone, placeProviderId, endPlaceProviderId, endDate) and gives no guidance on which omissions are meaningful, so several parameters remain explained only by 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?

"Changes an activity's details" gives a specific verb plus resource, and the immediately following clause scopes exactly which details change ("only the fields given change"). The move_activity sentence separates it cleanly from the sibling that handles relocation, so an agent can route without opening either schema.

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 names the alternative tool explicitly (move_activity) and the precise condition that selects it: moving to another day or lane, or reordering a day. That is a real exclusion, not a vague "use as needed", so an agent knows both when this tool applies and when it does not.

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.

Resources