Skip to main content
Glama

Undo last change

undo_last_change
Destructive

Undo the most recent change this assistant made in Weeklane (an add, update, completion, move, delete, bulk change, repeating-task change or Task Lock change), all of it at once. Use when the user says undo, revert or that the last change was wrong. Tasks the user changed in the app afterwards are left alone.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and idempotentHint=false, so safety is covered. The description adds genuinely new behavior: the undo is atomic across an entire bulk operation ('all of it at once') and deliberately does not clobber edits the user made afterward in the app. It stops short of saying what happens when there is nothing to undo, or whether the undo itself can be reversed.

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?

Two sentences, front-loaded with the scope of what gets undone, then the trigger and exclusion. The parenthetical list of change kinds is dense but each item rules out a different ambiguity, so nothing is wasted.

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, no-output-schema mutation whose destructive nature is already declared in annotations, the description covers what is undone, how much of it, and whose changes are excluded. Only the empty-history case and any redo capability are unaddressed, both minor for an agent deciding whether to call it.

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 there is no parameter meaning to add; the baseline for a no-param tool applies. The description usefully confirms there is no targeting argument by framing the operation as always acting on the single most recent change.

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 the most recent change this assistant made in Weeklane') and enumerates exactly which change kinds are covered, from add through Task Lock change. No sibling provides undo, so the scope statement alone is enough to distinguish it from the create/update/delete tools in the catalog.

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

Usage Guidelines5/5

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

Gives explicit trigger phrases ('undo, revert or that the last change was wrong') plus a boundary condition: tasks the user changed in the app afterwards are left alone. That tells the agent both when to call it and what it will and will not touch, which is the practical alternative-selection question for this tool.

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