Skip to main content
Glama

Calendar List Events

calendar_list_events

List calendar events within a specified ISO datetime range, with an optional result limit, to find scheduled activities for a given time window.

Instructions

Events in window (ISO datetimes).

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_iso": "<start_iso>",
      "end_iso": "<end_iso>"
    },
    "name": "calendar_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
end_isoYes
start_isoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no read-only confirmation beyond the implied 'list', no ordering, no pagination or limit behavior, no permission requirements. Only the notion of filtering to a window is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single fragment is short and front-loaded, but it is under-specified rather than concise; it omits information an agent needs, so brevity here costs more than it saves.

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

Completeness1/5

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

For a three-parameter tool with no annotations, no output schema, and zero schema descriptions, the description should explain inputs, return shape, and read semantics. It provides only an ISO-datetime format hint, leaving the definition inadequate 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% across three parameters, and the only hint given is '(ISO datetimes)', which does add real format information for start_iso and end_iso beyond the bare 'string' type. The default limit of 50 and the semantics of the window boundaries (inclusive/exclusive) remain completely undocumented.

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

Purpose2/5

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

The text 'Events in window (ISO datetimes)' is a noun fragment that largely restates the name calendar_list_events; it supplies no verb and does not distinguish this tool from any sibling such as mail_list_mailboxes. An agent can infer 'list calendar events in a time range' only by combining the fragment with the tool name.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no exclusions, and no mention of any alternative tool. Nothing tells the agent when to reach for calendar_list_events versus another listing or search tool.

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