Skip to main content
Glama

list_events

Retrieve calendar events overlapping a specified date range, optionally filtered by calendar, with defaults covering today through the next seven days.

Instructions

List calendar events overlapping a date range (default: today to +7 days).

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO 8601 range end. Default: now + 7 days.
fromNoISO 8601 range start. Default: start of today.
limitNo
calendarNoOnly this calendar name. Omit to read all writable calendars.
includeReadOnlyNoAlso include read-only calendars (holidays, birthdays). Slower.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries full burden; it does disclose the overlap matching rule and the default range, which are genuine behavioral facts. It never states that this is a non-destructive read, nor does it mention that 'limit' (max 500) can truncate results or that omitting 'calendar' fans out across all writable calendars.

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?

A single sentence with the resource, matching rule, and default window front-loaded, and zero redundant wording. Nothing could be trimmed without losing information.

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?

For a 5-parameter, read-only listing tool with no annotations and no output schema, the description covers the query semantics but omits the safety profile and result-size behavior. The schema handles most parameter detail, so this is adequate but with clear gaps around what an agent should expect back.

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?

Schema coverage is 80%, so a baseline of 3 applies, but the word 'overlapping' resolves a real ambiguity the schema leaves open: whether from/to match on event start time or on range intersection. That is meaningful semantics added beyond the schema, lifting it to a 4; the limit and calendar parameters are still only explained in the schema.

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 ('List') and resource ('calendar events') plus the matching criterion ('overlapping a date range'), which is enough to separate it from list_reminders and list_calendars without opening any schema. It stops short of explicitly distinguishing itself from those siblings, so a 4 rather than a 5.

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?

Usage is implied by the phrasing and the stated default window ('today to +7 days'), so an agent knows the typical invocation. There is no explicit when-to-use/when-not guidance and no mention of an alternative (e.g., querying a single calendar vs. all), so it remains minimum viable.

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