Skip to main content
Glama

Add an activity

add_activity

Adds an activity to the shared plan, or to a lane (laneId, from get_trip’s splits) for just the people in it. Times are local to the place; give a placeProviderId from search_places and its time zone is used. A flight or transport also arrives somewhere (endPlaceProviderId or endPlace), its end time local to there.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, local to the place; leave out to add it unscheduled
iconNoIts art from the app’s library, only when asked for: the app picks art by what it is (a sushi place gets sushi)
typeNoactivity
notesNo
placeNoWhere, as text, when it isn’t a place from search_places
titleYes
laneIdNoA lane from get_trip’s splits; leave out for everyone
tripIdYesThe trip’s id, from list_trips
endDateNoFor something over several days, its last day
endTimeNoHH:MM, 24-hour, local to the place
endPlaceNoWhere it arrives, as text, when it isn’t a place from search_places
timeZoneNoIANA zone, e.g. Asia/Tokyo; the place’s or the trip’s if left out
startTimeNoHH:MM, 24-hour, local to the place
endTimeZoneNoIANA zone its end date and time are in; the end place’s if left out
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: +{
      +  "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"
      +}
    • 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

A3.9/5.0
Behavior3/5

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

Annotations already establish this is a non-read-only, non-destructive, closed-world write. The description adds genuine behavioral context — times are local to the place, the place's time zone is adopted, and flights/transports have a separately-zoned arrival point — but says nothing about duplicate handling, whether the author needs edit rights, or any notifications/side effects on collaborators.

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?

Three sentences, no filler, with the primary placement behavior front-loaded and the timezone/lane rules following. Dense but every clause carries information an agent would otherwise have to infer.

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 16-parameter creation tool with only two required fields and an output schema, the description covers the non-obvious decisions: scheduled vs unscheduled, lane scoping, place-by-provider vs free text, and end-point semantics. Remaining parameters (icon, notes, type) are self-explanatory in the schema.

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?

With schema coverage at 81% the baseline is 3, and the description earns more: it explains that laneId comes from get_trip's splits and scopes visibility, that placeProviderId drives the time zone, and that endPlaceProviderId/endPlace apply specifically to flights and transport with a locally-zoned end time. That links otherwise independent fields into a coherent model.

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?

Opens with a specific verb+resource ("Adds an activity to the shared plan") and immediately narrows scope with the lane variant. It is clearly distinguishable from update_activity and move_activity by virtue of being a creation call, though it never names those siblings explicitly.

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 concrete selection context: use laneId from get_trip's splits to target a subset of people, and supply placeProviderId from search_places so the correct time zone is derived. It stops short of explicit when-not-to-use guidance or naming update_activity/remove_activity as alternatives for existing items.

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