Skip to main content
Glama

List Events

list_events
Read-onlyIdempotent

Retrieve events from your calendar within a specified date range. Filter by calendar name and control results with limit and offset.

Instructions

List events within a date range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateYesStart of range (ISO 8601, e.g. '2026-03-01T00:00:00Z')
endDateYesEnd of range (ISO 8601, e.g. '2026-03-31T23:59:59Z')
calendarNoFilter by calendar name
limitNoMax events to return (default: 100)
offsetNoNumber of events to skip (default: 0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYes
offsetYes
returnedYes
eventsYes
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds the date-range constraint. No contradictions or omitted behavioral traits given the simple listing operation.

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?

The description is a single sentence of 7 words, conveying the core purpose with zero filler. Every word earns its place.

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?

The tool has a simple operation with good annotations and output schema. The description covers the essential use case (listing events in date range). Minor omissions like sorting or pagination behavior are likely covered elsewhere.

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

Parameters3/5

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

Schema coverage is 100%, so the schema fully documents all 5 parameters. The description adds no parameter information beyond the schema, which meets the baseline.

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 clearly states the tool lists events within a date range, which specifies the verb, resource, and scope. However, it does not differentiate from sibling tools like 'search_events' or 'get_upcoming_events'.

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 description provides no guidance on when to use this tool versus alternatives, no contextual cues, and no when-not-to-use advice. It simply states the function.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/heznpc/AirMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server