Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

redo

Reapplies the most recent reverted backend or document operation when a forward history state exists, and refuses if no action is available.

Instructions

Redo the most recent reverted backend/document operation according to backend history semantics; refuses when no redoable state is available.

Side-effects: Re-applies reverted modification. Disambiguation: Single-step forward history navigation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Only readOnlyHint=false is provided, but the description steps in with the side-effect ('Re-applies reverted modification') and failure mode ('refuses when no redoable state is available'). It leaves out whether a redo is itself undoable and how it interacts with explicit transactions, which would have earned a 5.

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?

Three short, labeled lines with zero filler; the core action is front-loaded and the side-effect and disambiguation follow in a scannable order.

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?

For a no-parameter mutation tool that ships an output schema, the description covers the action, side-effect, failure condition, and its relation to sibling history tools. Nothing an agent needs to call it correctly is missing.

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?

The tool takes no parameters, and the schema correctly declares an empty object, so there is nothing for the description to disambiguate. That matches the baseline for zero-parameter tools.

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 (redo) applied to a specific resource (the most recent reverted backend/document operation) and scopes it to a single step. The 'Single-step forward history navigation' disambiguation line clearly separates it from the sibling undo tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tells the agent the precondition (a reverted operation must exist) and the refusal behavior when no redoable state is available. It falls short of explicitly naming undo as the counterpart alternative, though 'forward history navigation' implies the pairing.

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