Skip to main content
Glama

list_events

Read-only

Retrieve calendar events between start and end dates, sorted by start time, from one calendar or all calendars. Use ISO 8601 dates to query ranges up to 366 days.

Instructions

List events between 'start' and 'end', sorted by start time, from one calendar or all. Dates are ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00. A date-only 'end' includes that whole day. The range is at most 366 days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd of the range. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00
limitNoMost results to return. Default 50, maximum 500.
startYesStart of the range. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00
calendarNoCalendar name or id. Names ignore case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: results are sorted by start time and the range is capped at 366 days, which an agent needs in order to avoid a rejected query.

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?

Three short sentences, front-loaded with what the tool does, then format, then boundary semantics. No filler and nothing repeated from the schema verbatim beyond what needs clarifying.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with full schema coverage and annotations, this covers scope, ordering, format, and limits well. Absent an output schema, it could say a word about whether results are paginated or how the limit interacts with truncation, but nothing critical 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?

Schema coverage is 100%, so the baseline would be 3. The description still adds meaning the schema does not: a date-only 'end' covers the whole day, and the 366-day maximum range constrains start/end jointly, which no single parameter description conveys.

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?

The description gives a specific verb and resource ('List events') plus the range scoping, ordering ('sorted by start time'), and the 'one calendar or all' scope. That is enough to picture the tool, but it never names search_events as the contrasting option, so the boundary with the sibling search tool is left to inference.

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: query events across a date range, optionally narrowed to a calendar. There is no explicit when-to-use vs when-not, and no mention of search_events, which is the most likely alternative given sibling names.

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