Skip to main content
Glama

delete_event

DestructiveIdempotent

Borra un evento. Uno de Google u Outlook se borra también en ese calendario; si es una ocurrencia de una serie, sólo esa (la serie sigue). No borra los de Apple ni los que organiza otra persona (a esos se les rechaza la invitación desde la app).

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": "delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesUUID del evento
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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is known; the description adds real value beyond that by disclosing external propagation to Google/Outlook, partial-series semantics (only the occurrence dies, the series survives), and the silent-exclusion cases. It still does not say whether the deletion is reversible or what happens to linked entities such as tasks/reminders, which matters for an irreversible cross-provider delete.

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?

Three short sentences, front-loaded with the action, then scope semantics, then exclusions — every clause carries behavioral information. The opening clause about Google/Outlook is slightly compressed but understandable.

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 two-parameter destructive tool with no output schema, the description covers the essentials an agent needs before calling: it truly deletes externally, series behavior, and the cases where it will not act. Missing only return/error behavior and linked-entity side effects.

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 100% and both parameters (event_id, workspace_id) are documented in the schema itself, including the useful hint that workspace_id can be a name or omitted when the token is workspace-bound. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

Opens with a specific verb+resource ("Borra un evento") and immediately scopes it: events on Google/Outlook are also removed from those calendars, single occurrences of a series are removed alone, and Apple/organizer-owned events are never deleted. This lets an agent distinguish it from update/create siblings, though no sibling is named explicitly.

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 clear when-not conditions: Apple calendar events and events organized by someone else cannot be deleted, and the stated path for those is to reject the invitation from the app instead. It stops short of naming an alternative tool for those cases, so the routing guidance is implicit rather than explicit.

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