Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

List calendars

list_calendars
Read-onlyIdempotent

Lists the authenticated user's calendars—not events—so you can identify a calendar, get its CalDAV URL, and target it when creating, renaming, recoloring, or moving events.

Instructions

Lists the authenticated user's calendars — the calendars themselves, not the events on them. Use this to see which calendars exist before adding an event to a specific one, or to find the calendar to rename or recolor. Returns each calendar’s name, CalDAV URL and color when it has one; the URL is what create_calendar_event, update_calendar and move_calendar_events take. For the events on a calendar use list_calendar_events; to rename or recolor one use update_calendar; to move events onto one use move_calendar_events.

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: scope is limited to the authenticated user's own calendars, and the return payload is name, CalDAV URL and color when present, with the URL being the identifier other tools consume. It does not mention pagination or behavior when the user has no calendars, which keeps it short of a 5.

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 scope statement is front-loaded and each sentence carries routing or return-value information. There is mild redundancy between "use this to see which calendars exist before adding an event" and the closing sentence that names create_calendar_event, but the repetition is small and aids recall.

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?

This is a simple zero-parameter read tool with no output schema, so the description's job is to explain what comes back and when to call it. It does both, including the exact fields returned and the fact that the CalDAV URL is the handle other tools require.

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 and the description correctly does not invent any, so there is nothing to disambiguate. Baseline for a no-parameter tool applies.

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?

"Lists the authenticated user's calendars" is a specific verb+resource, and the clause "the calendars themselves, not the events on them" preempts the most likely confusion with list_calendar_events. It is clearly distinguishable from create_calendar and update_calendar as well.

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

Usage Guidelines5/5

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

Explicit when-to-use cases are given (check which calendars exist before creating an event, find a calendar to rename or recolor), and the final sentence routes the agent to the correct sibling for each alternative need: list_calendar_events, update_calendar, move_calendar_events. Nothing is left to inference.

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