Skip to main content
Glama

List calendar history

list_calendar_history
Read-only

The HISTORY of a project's calendar, newest first: every change of an event or of one of its occurrences — 'kind' (created, updated, deleted, occurrence, rollback), 'by' (the account), 'via' (the door: ui, api, mcp), 'source' and 'batch' (as the writer named them), 'at', and 'fields' — each field that changed with its value before and after (an occurrence changed apart is the field 'occ:20261123T150000Z'). With 'batches', the batches instead: how many changes and events each. Any member may read.

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": {
      "project": "<project>"
    },
    "name": "list_calendar_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchNoOnly the changes of this batch.
limitNoHow many, 1-200; default 50.
beforeNoOnly changes older than this change id — the next page.
batchesNotrue to list the batches instead of the changes.
eventIdNoOnly this event's changes, as 'eventId'.
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed world), and the description adds real context on top: newest-first ordering, the exact shape of each entry ('kind', 'by', 'via', 'source', 'batch', 'at', 'fields'), per-field before/after values, the 'occ:...' field convention for occurrence changes, and the permission needed to read. It stops short of describing volume characteristics or pagination behavior explicitly.

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

Conciseness4/5

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

One dense but front-loaded sentence that leads with what the tool returns and then details the payload. It is information-rich with little filler, though the em-dash cascade makes it harder to scan than a short structured list would be.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of describing return values — and it does so thoroughly, covering entry fields, ordering, per-field diffs, and the alternate batch mode. All six parameters are documented in the schema, and the access model is stated.

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 baseline would be 3, but the description adds genuine meaning: it explains that 'batches' switches the result to batch summaries with per-batch change and event counts, and that occurrence-level edits surface as an 'occ:...' field rather than a separate record. That is semantics the schema field text does not convey.

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 — the calendar HISTORY of a project, every change to an event or its occurrences — and enumerates the change kinds (created, updated, deleted, occurrence, rollback). That is enough for an agent to distinguish it from list_calendar_events (current state) without opening the schema.

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 wording 'HISTORY' and the batch/event filters, and the 'batches' mode is explained. However, it never says explicitly when to prefer this over rollback_calendar_batch, rollback_calendar_change, or list_calendar_events, and gives no exclusions or prerequisites beyond 'any member may read'.

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