Skip to main content
Glama

Undo a dream pass

dream_undo
Destructive

Revert a dream’s own changes within its 7-day undo window while leaving entries changed by other writers untouched.

Instructions

Undo a dream's own changes within its undo window (7 days).

    Entries another writer changed after the dream are listed under
    `conflicts` and left alone. Undoing a removed entry restores its
    value, type, importance and source; other metadata such as TTL or
    canonical flags is not restored (`metadata_restored: false`).
    

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": {
      "dream_id": "<dream_id>"
    },
    "name": "dream_undo"
  }
}

Input Schema

NameRequiredDescriptionDefault
dream_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.7.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag this as destructive and non-idempotent, and the description adds real substance on top: entries changed by another writer afterwards are surfaced as `conflicts` and left untouched, and restoration is partial — value, type, importance and source come back, but TTL and canonical flags do not. It stops short of saying whether the undo itself is reversible or what happens past the 7-day window.

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?

Front-loaded with the core action and window, then details on conflict handling and partial restoration. Every clause carries information, though the backticked field names make the second half denser than necessary.

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?

An output schema exists, so return values need not be spelled out, yet the description still calls out the `conflicts` and `metadata_restored` fields that matter for interpreting results. The main omission is post-window or failure behavior for a destructive mutation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single `dream_id` parameter, but the description's framing makes clear that it selects the dream whose changes are being reverted. No format, source, or lookup guidance is given for obtaining the id, so it only partially compensates for the coverage gap.

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 a dream's own changes') and scopes it to the dream's own mutations within a 7-day window, which distinguishes it from a generic rollback of arbitrary changes. An agent can identify the operation 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?

The 7-day undo window establishes an implicit eligibility condition, and the conflicts sentence tells the agent what will and will not be reverted. However, it never says when to choose this over siblings such as rollback or forget, nor what to do if the window has expired.

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