Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

undo

Revert recent AutoCAD COM actions by specifying how many steps to cancel; each step equals one MCP command.

Instructions

Отменить последние действия (только COM): steps шагов UNDO. Одна команда MCP = один шаг.

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

Input Schema

NameRequiredDescriptionDefault
stepsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses two useful traits — COM-only scope and the one-command-per-step semantics — but says nothing about what happens if steps exceeds available history, whether undo is itself reversible, or what side effects it has on the drawing. For a mutation tool with zero annotation coverage this is a meaningful gap.

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?

Two compact sentences, front-loaded with the core action, then the scope qualifier, then the step semantics. Nothing is wasted, though the telegraphic style ('steps шагов UNDO') is slightly awkward and could be clearer.

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

Completeness3/5

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

The tool is simple (one optional parameter) and an output schema exists, so return values need no explanation. Still, for a state-mutating undo operation with no annotations, the description omits failure/boundary behavior and reversibility, leaving an agent guessing about edge cases.

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% and the schema only labels the parameter 'Steps' with default 1, so the description's 'steps шагов UNDO' and 'one MCP command = one step' genuinely add meaning about how the value maps to undo depth. It still does not state valid ranges, upper bounds, or behavior for 0/negative values.

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?

States a specific verb and effect — 'Отменить последние действия' (undo the last actions) — which is unambiguous and clearly distinct from the drawing/export siblings. The '(только COM)' qualifier scopes the tool to COM-based sessions, adding useful precision, though it is not explained.

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?

Implies usage through the '(только COM)' restriction and the note that one MCP command equals one step, which tells the agent to use the steps parameter rather than repeated calls. However, there is no explicit when-to-use/when-not guidance or comparison to any alternative recovery path.

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