Skip to main content
Glama

update_event

DestructiveIdempotent

Cambia un evento (título, día, horario, descripción) o lo MUEVE de un calendario a otro con calendar.

Cambiar: en un evento local cambia la fila; en uno de Google u Outlook el
cambio viaja a ese calendario. Si es UNA ocurrencia de una serie (cada día
de una serie es su propio event_id), cambia sólo esa —lo que en Google es
«solo este evento»— y la serie sigue igual: para pasar la clase de hoy al
23, se cambia su start_date/end_date. No se cambian desde acá los de Apple
ni los que organiza otra persona.

Mover de calendario: `calendar` = 'Outlook', 'Google', el nombre o el mail
del calendario sincronizado, o 'local'. Se crea en el destino y se borra del
origen. No mueve eventos con invitados, ni de otra persona, ni una
ocurrencia suelta de una serie (eso es cambiarle la fecha, no el calendario).

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

Input Schema

NameRequiredDescriptionDefault
colorNoNombre ('blue') o hex ('#3b82f6')
titleNo
calendarNoMOVER el evento a este calendario: 'Outlook', 'Google', nombre o mail del calendario sincronizado, o 'local'
end_dateNo
end_timeNo
event_idYesUUID del evento
start_dateNo
start_timeNo
descriptionNo
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / calendar
      Added value: +{
      +  "description": "MOVER el evento a este calendario: 'Outlook', 'Google', nombre o mail del calendario sincronizado, o 'local'",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, idempotentHint=true and openWorldHint=true; the description earns credit by explaining that a move is implemented as create-in-destination plus delete-from-source (the concrete destructive behavior) and that edits on Google/Outlook events propagate to the remote calendar. It does not cover failure modes or partial-move rollback, which keeps it from a 5.

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?

Front-loaded with the two modes as labeled sections ('Cambiar:' / 'Mover de calendario:'), and each sentence carries a rule an agent could otherwise get wrong. It is longer than typical but not padded; the line breaks aid scanning more than they hurt.

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 10-parameter mutation tool with no output schema, the description covers the genuinely hard parts: cross-calendar propagation, occurrence-vs-series semantics, and the exact preconditions that block a move. It stops short of stating what a successful response returns or how failures on a mid-move are reported.

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 only 40% over 10 parameters, so the description must carry weight, and it does for the ambiguous ones: `calendar` gets accepted value forms ('Outlook', 'Google', name or synced-calendar email, 'local') and the meaning of start_date/end_date when shifting an occurrence is spelled out. Gaps remain for `color` and `workspace_id`, which the schema documents thinly and the description ignores.

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 opening sentence states a specific verb+resource (update an event) and names the two distinct modes: editing fields (title, day, time, description) or MOVING the event to another calendar via `calendar`. That distinction lets an agent separate this from create_event/delete_event without opening a 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 explicitly names when-not conditions: Apple events and events organized by someone else cannot be edited here, and events with guests, other people's events, or a lone series occurrence cannot be moved. It also routes the series-occurrence case ('para pasar la clase de hoy al 23') to start_date/end_date instead of `calendar`.

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