Skip to main content
Glama
nhype

OWA Exchange MCP Server

by nhype

update_meeting

Update an existing calendar meeting by cancelling and recreating it with new details. Modify subject, date, time, duration, location, description, or attendees while preserving unchanged fields.

Instructions

Update an existing calendar meeting.

Internally cancels the old meeting and creates a new one with updated fields, because OWA's JSON API does not support UpdateItem for calendar items reliably. Unchanged fields are preserved from the original meeting.

Args: item_id: The ItemId of the meeting to update (from get_calendar_events). subject: New subject (omit to keep original). date: New date in YYYY-MM-DD format (omit to keep original). start_time: New start time in HH:MM format (omit to keep original). duration_minutes: New duration in minutes (omit to keep original). location: New location (omit to keep original). description: New description/body text (omit to keep original). required_attendees: Email addresses for required attendees. Replaces existing list. Omit to keep original attendees. optional_attendees: Email addresses for optional attendees. Replaces existing list. Omit to keep original attendees. change_key: Ignored (kept for backward compatibility).

Returns: JSON object with update result including new item_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes
subjectNo
dateNo
start_timeNo
duration_minutesNo
locationNo
descriptionNo
required_attendeesNo
optional_attendeesNo
change_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description fully discloses the non-obvious behavior: internally cancels and recreates, preserves unchanged fields, and ignores change_key. Since no annotations are provided, this transparency is critical.

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?

The description is well-structured with a summary, internal behavior note, and parameter list. It is slightly lengthy but every sentence adds value. Could be marginally more concise.

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

Completeness5/5

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

Given the complexity (10 parameters, internal side effects), the description is complete: it covers all parameters, return value, and critical behaviors. No gaps remain.

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

Parameters5/5

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

All 10 parameters are described in detail, including format hints (YYYY-MM-DD, HH:MM), omission behavior, and that attendee lists replace existing ones. This compensates for 0% schema description 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?

The description clearly states 'Update an existing calendar meeting' and details the internal behavior of cancelling and recreating. It effectively distinguishes from siblings like 'create_meeting' and 'cancel_meeting'.

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 description explains when to use the tool (to update a meeting) and notes that it replaces the old meeting. It implicitly warns that attendee lists are replaced. However, it does not explicitly state when not to use it or compare to alternatives like 'respond_to_meeting'.

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/nhype/owa-exchange-mcp'

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