msgraph-mcp

by jspv

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

list_calendars

List readable calendars for the current user. Provide a user_id to access another user's shared calendars.

Instructions

List readable calendars. Pass user_id for shared calendars (e.g. another user's email or object ID).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_calendars"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	No
`account_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Without annotations, the description must disclose behavior but only says 'List readable calendars'. It does not mention whether it returns all calendars, pagination, authentication requirements, or any side effects. The read-only nature is implied but not explicit.

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 sentences with clear front-loading of purpose and no unnecessary words. Every sentence adds value.

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?

Given the presence of an output schema that likely describes return values, the description provides the essential purpose and a key usage hint. However, for a list tool in a complex domain, more context like scope of calendars returned (own vs. shared) would improve completeness.

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 description adds meaning for user_id by explaining its use for shared calendars with an example, but account_id is left unexplained. Schema description coverage is 0%, so this partial help is welcome but insufficient for full parameter understanding.

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?

Description clearly states verb 'List' and resource 'readable calendars', distinguishing from sibling tools like list_events or get_event which operate on events, not calendars.

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 guidance to pass user_id for shared calendars, which is helpful for usage, but does not specify when not to use this tool or compare with alternatives like list_events for calendar-related queries.

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