Skip to main content
Glama

studio_undo

Revert the last committed canvas transaction and synchronize the browser and disk so the design returns to its prior state.

Instructions

撤销最近一次已提交的画布事务并同步浏览器与磁盘。

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

Input Schema

NameRequiredDescriptionDefault
urlNo
portNo
clientIdNo
projectDirNo
expectedHeadTxIdNo
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's job is to add context, and it does explain that both the browser view and on-disk state are synchronized. It omits what an agent most needs for a mutation: whether uncommitted edits survive, what happens on an empty undo stack, and whether the operation can fail mid-sync. The 'sync browser and disk' note also sits in mild tension with destructiveHint=false, since reverting a committed transaction does change persisted state, though the presence of studio_redo makes the revert conventional and reversible.

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?

A single sentence that front-loads the operation and appends the side effect. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a state-mutating tool with six undocumented parameters, no output schema, and no annotation coverage of preconditions. One sentence about the target transaction is insufficient — an agent cannot tell how to satisfy the expectedHeadTxId/expectedRevision guards or how failures are reported.

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

Parameters2/5

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

All six parameters have zero schema description coverage and the description explains none of them. The phrase 'most recently committed transaction' faintly gestures at expectedHeadTxId, but url, port, clientId, projectDir and expectedRevision are left entirely opaque, including the concurrency-guard role of expectedRevision.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource — undo the most recently committed canvas transaction — and adds the side effect of syncing browser and disk. It is clearly distinct from studio_redo, though it never names that sibling explicitly.

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?

Scope is implied by 'most recently committed transaction', which tells the agent this is a single-step revert rather than a general rollback. However, there is no explicit when-to-use guidance, no pointer to studio_redo as the inverse, and no statement about what happens when there is nothing to undo.

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

Deploy Server

Other Tools