Skip to main content
Glama

owa_undo

Reverts changes made through these tools, restoring deleted, renamed, or edited songs, slides, notes, passages, run sheets, or media. List recent changes, then undo a specific id or the newest one.

Instructions

Put back a change made through these tools -- a song, slide document, slide, note, saved passage, run sheet or media file that was deleted, changed, renamed or created. list shows the recent changes, newest first, each with an id; undo puts back change id, or with no id the newest one not yet undone. An undo is itself a change in the list, so it can be undone too. The user's own edits in the app are undone with Ctrl+Z, not this.

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

Input Schema

NameRequiredDescriptionDefault
idNoA change id from list
pageNo
actionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.9/5.0
Behavior5/5

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

Since no annotations are provided, the description provides crucial behavioral context. It specifies that an undo operation itself becomes an item that can subsequently be undone, indicating a persistent history mechanism. It also explains the logic for targeting the newest change if no ID is provided.

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?

The description is highly efficient, front-loading the tool's core functionality and then structuring the explanation logically. Each sentence serves to define the tool's scope, mechanism, or limitations, resulting in zero wasted words.

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?

The description provides all necessary context for an agent to understand how this state-management tool functions. It defines the recoverable content, the action space, and the recursive nature of the undo function, which are key behavioral complexities.

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?

Given the low schema coverage (33%), the description adds significant semantic weight. It defines the functional intent of the `action` parameter (`list` vs `undo`) and explains the cascading logic applied when the `id` parameter is omitted, which is not clear from the schema alone.

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?

The description clearly states that the tool reverts changes (deletion, modification, creation, renaming) made through other tools. It comprehensively lists the types of content affected, such as slides, notes, and media files, and defines the two modes of operation: `list` and specific `undo`.

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?

It provides explicit instructions on using the different functions: use `list` to view recent changes, and use `undo` with an `id` or no `id` for the newest entry. Furthermore, it distinguishes this tool's behavior from the user's standard application undo (Ctrl+Z).

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