Skip to main content
Glama

Edit an event invite

status_update_event
DestructiveIdempotent

Change the title, details, place, date, time or theme of an event invite made with status_create_event. Send eventId, editKey and only the fields to change. The invite link stays the same and guests see the change straight away. Does not change a date poll, the guest list or costs, and cannot cancel or delete the event.

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": {
      "eventId": "<eventId>",
      "editKey": "<editKey>"
    },
    "name": "status_update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoEvent date as YYYY-MM-DD. Leave out if the date is not set yet
timeNoStart time as 24-hour HH:mm, local to timeZone, e.g. 19:30. Needs date
themeNoVisual style of the invite page: party, dinner, garden, sport, holiday, plain. Defaults to party
titleNoEvent name shown at the top of the invite, e.g. "Sam's 30th" or "Book club dinner"
detailsNoInvite message for guests: what is happening, what to bring, dress code, cost per person
editKeyYeseditKey returned by status_create_event
eventIdYeseventId returned by status_create_event
locationNoVenue name or address, e.g. "The Albion, Bristol"
timeZoneNoIANA time zone for date and time, e.g. Europe/London (the default) or America/New_York

Output Schema

NameRequiredDescriptionDefault
eventYesThe event as guests see it
messageYesPlain-language summary of the result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare that this is a non-read-only, idempotent, destructive-capable update. The description adds useful behavior beyond those annotations: the invite link stays the same, guests see changes immediately, and the update is scoped away from polls, guest lists, costs, cancellation and deletion. It does not explicitly say that changing a field overwrites its previous value, which is the main remaining behavioral gap.

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?

The description is four tight sentences, front-loads the editable fields and required identifiers, then adds effect and scope constraints. Every sentence carries useful information and there is no filler.

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 nine-parameter update tool with full schema descriptions, annotations and an output schema, the description supplies enough context to invoke it correctly: what can change, which identifiers are required, how guests are affected, and what the tool cannot do. Return values are covered by the output schema, so no description gap remains.

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?

Schema coverage is 100%, so the schema already documents all nine parameters. The description still adds meaningful semantics by saying to send only the fields to change and by identifying eventId and editKey as the required identifiers from status_create_event. It does not add format details beyond the schema, but the partial-update instruction is valuable.

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 uses a specific verb and resource: 'Change the title, details, place, date, time or theme of an event invite'. It explicitly ties the tool to status_create_event and distinguishes editing from creating or reading an event, so an agent can identify its role without opening the 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 states exactly what to send ('eventId, editKey and only the fields to change') and gives clear exclusions: it does not change a date poll, guest list or costs, and cannot cancel or delete the event. The reference to status_create_event also makes the create-vs-edit boundary clear.

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