Skip to main content
Glama

List Calendars

list_calendars
Read-only

List your own and shared Microsoft 365 calendars, returning calendar IDs for event tools and flagging the default calendar and any calendars you cannot edit.

Instructions

List the calendars you can see: your own, and any shared with you. Returns each calendar's ID for the calendar_id parameter of the event tools, and marks the default calendar and any you cannot edit.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds behavior beyond that: it discloses the key output fields (calendar ID), flags the default calendar, and flags calendars the caller cannot edit. That permission-adjacent detail is valuable since there is no output schema; only return ordering/pagination is unaddressed.

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 short sentences, front-loaded with what is listed and followed by what the result is useful for. Every clause carries information: scope, output identifiers, default marking, and edit-permission marking.

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?

With no output schema, the description must cover return values, and it does: IDs, default flag, and non-editable flag. For a zero-parameter read tool with annotations covering safety, nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing arguments.

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?

States a specific verb and resource ("List the calendars you can see") and narrows the scope to personal plus shared calendars, so an agent knows exactly what comes back. It does not explicitly name a neighbouring alternative such as list_calendar_view, so the differentiation is implied by scope rather than stated.

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?

Gives clear usage context by explaining the tool's role in a workflow: it supplies the calendar_id needed by the event tools. It does not state preconditions or when-not to use it (e.g., versus a calendar-view listing), leaving that inference to the agent.

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

Deploy Server

Other Tools