Skip to main content
Glama

forward-calendar-event

Destructive

Forward a meeting event to additional recipients. Notifies the organizer and adds the new recipient to the attendee list when done by an attendee.

Instructions

This action allows the organizer or attendee of a meeting event to forward the meeting request to a new recipient. If the meeting event is forwarded from an attendee's Microsoft 365 mailbox to another recipient, this action also sends a message to notify the organizer of the forwarding, and adds the recipient to the organizer's copy of the meeting event. This convenience is not available when forwarding from an Outlook.com account.

💡 TIP: Forwards a meeting invitation to additional recipients. Body: { ToRecipients: [{ emailAddress: { address, name } }], Comment (optional) }. If the forwarder is an attendee (not organizer), the organizer is also notified and the new recipient is added to the organizer's attendee list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
eventIdYesPath parameter: eventId
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
Behavior4/5

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

Annotations indicate destructive and open-world behavior. Description adds details about notifying organizer and adding recipient to organizer's copy, and notes Outlook.com limitation. Adds value beyond annotations.

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?

Concise with a tip; front-loaded with key action. Minor redundancy (first paragraph restates tip) but overall efficient.

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?

Covers main action and side effects, but omits explicit return value details (no output schema), and does not explain includeHeaders/excludeResponse parameters. Some behavioral aspects (original event state) not addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description includes a tip showing body structure and optional Comment, adding context beyond schema. It explains behavioral implications of parameters (attendee vs organizer) but doesn't cover includeHeaders/excludeResponse.

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?

Description clearly states 'forward the meeting request to a new recipient,' specifying action and resource. It distinguishes from sibling tools like 'forward-mail-message' by focusing on calendar events, and includes platform-specific behavior (Outlook.com).

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?

Provides context on organizer vs. attendee forwarding and notification behavior, but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives like accept/decline/cancel calendar events.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Softeria/ms-365-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server