Skip to main content
Glama

List calendar events

event_list
Read-onlyIdempotent

List workspace calendar events, including upcoming and the past 90 days. These are calendar events, not email delivery events. Requires API key scope: read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered upstream. The description adds genuinely new behavior: the 90-day lookback window on results and the required "read" API key scope, both of which affect whether a call succeeds and what it returns. It does not mention pagination, result limits, or ordering, which is the remaining gap.

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 the verb and resource, then the scope window, then the disambiguation and auth requirement. Every sentence carries information that changes how an agent would call the tool; nothing is redundant with the title or annotations.

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 zero-parameter, read-only listing tool whose annotations already cover safety, the description supplies the scope window and auth scope, which is close to everything an agent needs. With no output schema, a brief note on result shape or pagination would close the last gap, but it is not a serious omission.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description needs to supply. The absence of any filtering arguments is worth noting but is a schema fact, not a description failure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List workspace calendar events") plus a scope bound (upcoming and the past 90 days). It also pre-empts a real source of confusion by declaring these are calendar events, not email delivery events, so an agent can distinguish it from the email-oriented siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear context for use and an explicit exclusion (not email delivery events), which is the main ambiguity for a tool named event_list in a catalog full of email tools. It stops short of naming alternatives for event mutations (create/update/cancel) or describing how it differs from events_recent, so guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources