Get all available calendars across connected accounts, optionally filtered by a specific account ID to focus on relevant schedules.
List calendars across all accounts, optionally filtered by account_id.
| Name | Required | Description | Default |
|---|---|---|---|
| account_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of explaining behavior. It usefully discloses the broad scope ('across all accounts') and the optional filtering behavior. However, it does not address pagination, permissions, or behavior with invalid account_id values, though these may be less critical for a simple list operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that places the core action and scope first and appends the optional filter condition. Every word contributes useful information with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with one optional parameter and an output schema, the description covers the key invocation details: what is listed and how the parameter affects scope. It does not mention where account_id values come from (e.g., list_accounts), but that is not strictly necessary for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must add meaning to the lone parameter. It does this by explaining that account_id optionally filters the results across all accounts. This provides essential semantic context beyond the bare schema definition.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and resource ('calendars'), and clarifies scope ('across all accounts') along with an optional filter. This clearly distinguishes it from sibling tools like list_accounts and get_events, which target different resources.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool is for listing calendars and that account_id can optionally restrict results, but it does not explicitly name alternatives or state when not to use it. An agent could infer the distinction from sibling names, but the guidance is not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.