Skip to main content
Glama

calendar list events

calendar_list_events
Read-onlyIdempotent

Lists calendar events within a specified time window, with optional free-text filtering and calendar selection, to help review schedules and find relevant meetings.

Instructions

List events in a time window (RFC3339), optionally filtered by free-text query.

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": "calendar_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
time_maxNo
time_minNo
calendar_idNoprimary
max_resultsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered without description help. The description adds only the RFC3339 format expectation and the optionality of the query filter; it says nothing about pagination, empty-result behavior, or the fact that calendar_id defaults to 'primary'. With annotations doing the heavy lifting, a 3 is appropriate.

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 the core action first and the qualifier second; no filler or redundancy. It is arguably too terse for a five-parameter tool, but nothing in it is wasted.

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?

An output schema and rich annotations relieve the description of explaining returns and safety, and the format hint for timestamps is genuinely useful. However, with 5 parameters at 0% schema coverage and two of them unmentioned, the definition is only minimally sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so all five parameters depend on the description for meaning. It covers the time window (time_min/time_max, RFC3339) and the free-text query, but says nothing about calendar_id (default 'primary') or max_results (default 25), leaving two parameters entirely unexplained.

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 events') plus a scope ('in a time window'), which is enough to separate it from calendar_create_event, calendar_get_event or calendar_check_availability. It stops short of explicitly naming a sibling it is not, so it is clear but not maximally differentiated.

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 phrase 'optionally filtered by free-text query' implies the query parameter is a refinement of a time-window listing, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives like calendar_check_availability or calendar_get_event. The agent must infer the selection rule from the name alone.

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