Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

calendar

Manage Microsoft 365 events by listing, creating, retrieving, updating, or deleting them with attendees, locations, and recurrence options.

Instructions

Manage calendar events: list, create, get, update, or delete

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": {
      "operation": "<operation>"
    },
    "name": "calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date/time in ISO format (for create/update)
startNoStart date/time in ISO format (for create/update)
contentNoEvent body content in HTML (for create/update)
eventIdNoEvent ID (for get/update/delete)
subjectNoEvent subject (for create/update)
locationNoEvent location (for create/update)
attendeesNoAttendee email addresses (for create)
operationYesThe operation to perform
maxResultsNoMaximum number of results (default: 10)
recurrenceNoRecurrence pattern and range for recurring events
endDateTimeNoEnd date/time filter in ISO format (for list)
startDateTimeNoStart date/time filter in ISO format (for list)
isOnlineMeetingNoCreate as Teams meeting (for create/update)
sendCancellationsNoSend cancellation notices (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and delivers almost none of it. It does not disclose that delete is destructive, that create/update with attendees may send invites, that sendCancellations defaults to true, or what permissions are needed. An agent must infer all side effects from the bare verb list.

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?

A single front-loaded sentence with no filler or repetition. It is efficiently written, though the extreme brevity for a 14-parameter multi-operation tool edges toward under-specification rather than crispness.

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

Completeness1/5

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

With 14 parameters, a nested recurrence object, no annotations, and no output schema, a one-line description is inadequate. Nothing tells the agent which fields are required per operation, that list uses startDateTime/endDateTime while get uses eventId, or what a successful call returns.

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 the schema already labels every parameter with its applicable operations (for create/update, for list, etc.), so the description adds nothing but also loses nothing. Baseline 3 is correct when the schema does all the parameter work.

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?

"Manage calendar events" is a clear verb+resource, and the enumeration of operations (list, create, get, update, delete) makes the tool's scope explicit. It separates itself from siblings like mail or planner by resource, though it never distinguishes itself from teams_meeting, which plausibly overlaps on meeting creation.

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

Usage Guidelines2/5

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

The description lists the operations but gives no guidance on when to choose this tool over calendar-adjacent siblings such as teams_meeting or planner. There is no mention of prerequisites, no exclusions, and no hint about which parameters each operation expects.

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