Skip to main content
Glama
Sign In
ews-outlook-mcp

ews-outlook-mcp

by devsergioherrera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Eliminar evento de calendario

ews_delete_event
Destructive

Delete a calendar event from an Outlook/Exchange mailbox. Optionally send cancellation notices to attendees.

Instructions

Elimina un evento del calendario (DeleteItem). Si tiene invitados, les envía cancelación por defecto.

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>"
    },
    "name": "ews_delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesId del evento a eliminar
notifyAttendeesNoSi es true (default), envía cancelación a los invitados; si es false, elimina en silencio

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds valuable behavioral context: that attendees receive cancellation by default, which is not inferable from the annotations. No contradiction.

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?

Two short sentences, front-loaded with the main action, no unnecessary words. Efficient and clear.

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 simple delete tool with two parameters and no output schema, the description plus annotations provide sufficient context. The attendee-notification behavior is a key extra. Irreversibility is covered by destructiveHint.

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?

The schema covers 100% of parameters with descriptions. The description restates the default of notifyAttendees ('por defecto') but does not add significant new semantics beyond the schema. Baseline 3 is appropriate.

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 'Elimina' (delete) with a clear resource 'evento del calendario' (calendar event), and includes the EWS operation name (DeleteItem). This clearly distinguishes it from sibling tools like ews_update_event or ews_create_event.

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?

The context is clear: this is the tool for deleting calendar events, with an additional note about notifyAttendees default behavior. However, it does not explicitly mention alternatives or when not to use it, but the deletion purpose is evident.

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

Deploy Server

Other Tools