ews-outlook-mcp

Aceptar invitación a reunión

ews_accept_event

Accepts a received meeting invitation using its ItemId. Optionally sends a comment to the organizer.

Instructions

Acepta una invitación de reunión recibida (por ItemId del mensaje de invitación).

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_accept_event"
  }
}

Input Schema

Name	Required	Description	Default
`comment`	No	Comentario opcional para el organizador
`eventId`	Yes	ItemId de la invitación/reunión a aceptar

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations already indicate this is not read-only and not destructive, so the description adds no extra behavioral context. It does not mention side effects (e.g., sending a response to the organizer or updating the calendar), missing an opportunity to enrich the agent's understanding.

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?

The description is a single, front-loaded sentence with no redundant information. It efficiently communicates the purpose and the input mechanism.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter accept action, the description, schema, and annotations provide a basic functional picture. However, it lacks usage differentiation and behavioral side-effect context, leaving some gaps for a fully self-contained understanding.

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 coverage is 100% with both eventId and comment described. The description mentions the ItemId input but adds no additional semantic value beyond the schema, so the baseline of 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 clearly states the tool accepts a received meeting invitation using the ItemId, which is a specific verb+resource combination. It distinguishes from sibling tools like ews_decline_event (declines) and ews_update_event (updates).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by indicating it operates on a received invitation, but it does not explicitly state when to use this tool versus alternatives like accept vs decline. No exclusions or alternative references are provided.

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

Deploy Server