Skip to main content
Glama

Add Event

add_event

Add something to do during the trip — a museum, concert, restaurant, tour or activity. Events belong to the variant rather than to a single destination, and can be scheduled with start/end times or left unscheduled as ideas.

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

Input Schema

NameRequiredDescriptionDefault
dataYesThe event to add.
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. Changed1 schema field changed
    • addedInput schema / properties / data / properties / priceOptions
      Added value: +{
      +  "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.",
      +  "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"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent creation call, so the safety profile is covered. The description adds real behavioral context — variant-scoped ownership and the fact that start/end are optional — but is silent on whether repeated calls create duplicates, what identifier comes back, and whether image/link inputs are validated. Adequate but thin for a mutation tool.

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, and the resource definition is front-loaded ahead of the ownership/scheduling nuance. Nothing repeats the name or the annotations.

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 create tool with a deeply nested but fully documented schema and a clear annotation profile, the description supplies the conceptual model an agent needs (variant-level, optionally scheduled). The only gap is the absence of any statement about the return value, which matters because there is no output schema.

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?

With schema description coverage at 100%, the schema already explains name/notes/priceOptions/currency/location precedence rules in detail. The description only contributes the meaning that start/end may be omitted (leaving the event an unscheduled idea) and that the event is keyed to a variant. Baseline 3 applies since the schema does the heavy lifting.

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?

The description states a concrete verb and resource with concrete examples ("a museum, concert, restaurant, tour or activity") and clarifies the ownership model — events attach to a variant, not a destination. That scope statement implicitly separates it from add_destination and add_accommodation_option, though no sibling is named explicitly, which keeps it just 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?

It gives useful context about where events live (variant-level) and that they may be scheduled or left as unscheduled ideas, which tells the agent what kinds of things qualify. It does not say when to prefer this over update_event, add_destination_option, or add_accommodation_option, nor any prerequisite (that the trip and variant must exist and the ids come from list_trips/get_trip).

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.