Skip to main content
Glama

studio_redo

Restore the most recently undone canvas transaction and synchronize the browser view with saved disk 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_redo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
portNo
clientIdNo
projectDirNo
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description usefully adds that the operation synchronizes both the browser and disk, which is real behavioral context beyond the annotation set. It does not say what happens on a revision conflict, whether the redo is limited to a single level, or how sync failures are surfaced.

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?

The definition is a single front-loaded sentence that states the action before its side effects, with no filler. It is efficient, but it is arguably under-specified rather than concise, so it falls short of a 5.

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 five undocumented parameters and no output schema. The description says nothing about how the revision guard works, what the required connection parameters are, or what is returned after the redo. For this complexity, the description is not complete enough for an agent to invoke the tool confidently.

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 five parameters, url, port, clientId, projectDir, and expectedRevision, have 0% schema description coverage, and the description explains none of them. The most consequential one, expectedRevision, is an optimistic-concurrency guard whose semantics and failure behavior are entirely undocumented. Given that the schema description coverage is 0%, the description should compensate for that gap but does not.

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 states a specific verb and resource: redo the most recently undone canvas transaction, and it also names the side effects (syncing the browser and disk). This is clear enough to distinguish it from the mutation siblings, but it never names studio_undo as its inverse, so the pairing has to be inferred.

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 phrase 'most recently undone' implicitly constrains when the tool applies, since there must be an undo in history for it to work. However, there are no explicit preconditions, no statement of what happens when nothing has been undone, and no routing to studio_undo or studio_apply_commands as alternatives.

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