Skip to main content
Glama

create_event

Crea un evento en el calendario de la persona.

Si tiene un calendario sincronizado (Outlook, Google, Apple) el evento se
crea POR ÉL —en el proveedor, con lo que eso implica— y no en el calendario
local del workspace. Con varios, elige el que mejor aplica: el que la
persona nombre en `calendar` («Outlook», «Google», el nombre o el mail
del calendario) o, sin pedido, el marcado como destino por defecto. Sólo si
no hay ningún calendario sincronizado queda LOCAL (lo ven los miembros del
workspace). La respuesta dice en qué calendario quedó.

Sin hora es un evento de día completo, que es el default. Con `start_time`
pasa a tener horario.

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": {
      "title": "<title>",
      "start_date": "<start_date>"
    },
    "name": "create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoColor del evento si queda local: un nombre como 'blue' o un hex '#3b82f6'. En un calendario sincronizado manda el color del calendario
titleYesTítulo del evento
calendarNoEn qué calendario sincronizado: 'Outlook', 'Google', el nombre o el mail del calendario. Omitir = el destino por defecto de la persona (nunca el local si hay uno sincronizado)
end_dateNoDía de fin, YYYY-MM-DD (para eventos de varios días)
end_timeNoHora de fin 'HH:MM'
start_dateYesDía, YYYY-MM-DD
start_timeNoHora de inicio 'HH:MM' (omitir = día completo)
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. Changed2 schema fields changed
    • addedInput schema / properties / calendar
      Added value: +{
      +  "description": "En qué calendario sincronizado: 'Outlook', 'Google', el nombre o el mail del calendario. Omitir = el destino por defecto de la persona (nunca el local si hay uno sincronizado)",
      +  "type": "string"
      +}
    • changedInput schema / properties / color / description
      Previous value: -"Color del evento: un nombre como 'blue' (el default de la app) o un hex '#3b82f6'"New value: +"Color del evento si queda local: un nombre como 'blue' o un hex '#3b82f6'. En un calendario sincronizado manda el color del calendario"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the event is written in the external provider ("se crea POR ÉL —en el proveedor, con lo que eso implica—"), that a LOCAL event is visible to workspace members, that the default is an all-day event, and that the response reports which calendar was used. These are exactly the consequences an agent needs before writing, and they exceed what readOnlyHint=false / openWorldHint=true convey.

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?

The core behavior is front-loaded in the first sentence and the fallback hierarchy follows logically. It is somewhat long with heavy parentheticals and em-dash asides, but each sentence carries real routing or behavioral information rather than restating the schema.

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 9-parameter mutation tool with no output schema, it covers the key ambiguity (where the event physically lands, and how the caller learns that) as well as the all-day default. It does not address permission/auth requirements or failure modes for provider-synced writes, which for an openWorldHint tool would have been worth a line.

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 description coverage is already 89%, and the parameters the description touches (`calendar`, `start_time`) are documented in the schema with nearly identical wording. The description adds the multi-calendar selection heuristic around `calendar`, but provides no meaning for undocumented params like `description` or clarifications on date/time combination beyond the schema.

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 first line states a concrete verb and resource ("Crea un evento en el calendario de la persona") and the rest of the text sharpens what kind of creation it is. It never names siblings like update_event or create_meeting, so the boundary with those tools must be inferred from the verb alone.

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?

It gives explicit routing rules: with several synced calendars, use the one the person names in `calendar` or the default destination, and only fall back to LOCAL when no synced calendar exists. What is missing is guidance relative to alternatives such as update_event or create_meeting; the when-to-use is internal to this tool rather than cross-tool.

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