Skip to main content
Glama
Sign In

secondbrain

by media.secondbrain
OverviewDiscussionsAdmin

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.

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
Behavior4/5

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

Annotations already declare non-destructive/non-readOnly/openWorld=false, so the bar is lower; the description still adds meaningful behavior: provider-side creation, workspace visibility of LOCAL events, and that the response reports the resulting calendar. It omits what "con lo que eso implica" concretely entails (invites/notifications) and any permission requirements.

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 core action, then routing, then defaults; most sentences earn their place. Slightly long and partly restates schema semantics ("Sin hora es un evento de día completo"), but structure is logical.

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 mutation tool with no output schema, it covers destination routing, visibility implications, fallback behavior, and the response payload. Remaining gaps (attendees, errors, duplicates) are minor given the tool has no attendee parameter.

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 89%, so the schema already documents `calendar`, `color`, `start_time`, etc. The description reinforces the all-day-vs-timed default tied to `start_time`, but adds little syntax or format detail beyond the schema — baseline 3 for high coverage.

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?

States a specific verb and resource ("Crea un evento en el calendario de la persona") and immediately scopes where the event actually lands (synced provider vs local workspace calendar). An agent can distinguish this from create_meeting/update_event on the resource 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?

Gives concrete selection logic: pick the synced calendar named in `calendar`, otherwise the default destination, and fall back to LOCAL only when no synced calendar exists. Solid context, but no explicit when-not guidance or named alternatives (e.g., update_event vs create_event).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All secondbrain toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources