Skip to main content
Glama

Rollback calendar batch

rollback_calendar_batch
Destructive

Undo EVERY change of one batch in one call — e.g. a solver's layout of the week, written with batch='solver 2026-11-18'. Each event goes back to how it was before the batch's first change of it, field by field; a field somebody changed after the batch keeps their change, and 'kept' names those events, the fields and who. 'restored' lists the events put back. Anybody who may write in the project.

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>",
      "batch": "<batch>"
    },
    "name": "rollback_calendar_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchYesThe batch, as the writes named it.
projectYesThe project key, e.g. TH.
confirmOverCeilingNotrue to let the rollback take a week over the ceiling — only for somebody who configures the project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the operation's real semantics: each event reverts field by field to its pre-batch state, and fields changed later by someone else are preserved. It also explains that 'kept' reports conflicts with who made them and 'restored' lists reverted events — return-shape information that no output schema provides — plus the write-permission requirement.

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?

The destructive action and its scope are front-loaded in the first clause, and each following sentence covers revert semantics, conflict handling, and permissions. Dense and largely waste-free, though the mixing of field semantics and return-field names in one sentence is slightly cluttered.

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?

For a destructive, no-output-schema mutation, the description supplies everything an agent needs: what is undone, how partial conflicts resolve, what the response contains, and who may call it. Nothing material is left to inference.

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 parameters are already documented, but the description adds the batch identifier's format via the example 'solver 2026-11-18' and clarifies confirmOverCeiling is limited to someone who configures the project — a permission constraint beyond the schema's wording.

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 — 'Undo EVERY change of one batch' — with a concrete example of a batch value. The word 'EVERY' plus 'batch' distinguishes it from the sibling rollback_calendar_change, which by name alone handles a single change.

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?

Clearly frames the use case (bulk undo of one batch in one call) and gives an example batch identifier, which tells the agent the precondition of knowing the batch name. It states the authorization condition ('Anybody who may write in the project') but never explicitly says when to prefer this over rollback_calendar_change.

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