Skip to main content
Glama

Rollback calendar change

rollback_calendar_change
Destructive

Undo ONE change of a project's calendar (an id from list_calendar_history), field by field: what is still as the change left it goes back; a field somebody changed since keeps their change, and the answer names that event under 'kept' with the fields and who. An event the change made goes (unless changed since); one it deleted comes back under its id. The rollback is a change of its own and can be undone the same way. Under the weekly ceiling of reconfigurations like any write. 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>",
      "changeId": "<changeId>"
    },
    "name": "rollback_calendar_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesThe project key, e.g. TH.
changeIdYesThe change's id.
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 only flag destructiveHint=true; the description goes well beyond that by explaining the partial-rollback rule (fields still as the change left them revert, fields edited since keep the user's change), what happens to created and deleted events, and that the rollback is itself a reversible change. It also discloses the rate/ceiling constraint and who is authorized.

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?

Telegraphic but front-loaded: the core one-change undo rule comes first, then the kept-event behavior, then constraints. Every clause carries information, though the compressed phrasing takes a second read in places.

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?

No output schema exists, and the description compensates by naming the response's 'kept' key with its fields and actor. Combined with the permissions, ceiling, and reversibility notes, an agent has everything needed to call this destructive tool correctly.

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 the baseline is 3; the description earns more by giving changeId a concrete source (an id from list_calendar_history) and by tying confirmOverCeiling to the weekly ceiling and the project-configurer permission, which the schema only hints at.

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 ONE change of a project's calendar") and pins down the input's provenance ("an id from list_calendar_history"). The emphasis on ONE distinguishes it from the batch sibling rollback_calendar_batch without needing to open either 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?

Tells the agent where the changeId comes from (list_calendar_history) and gives the execution conditions: the weekly reconfiguration ceiling and the permission requirement ("Anybody who may write in the project"). It stops short of explicitly naming the batch alternative for multi-change undos, so the exclusion is only implied.

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