Skip to main content
Glama
Sign In
duddy

duddy

by qu15501267889-sketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

duddy_rollback_plan

Undo completed node-creation and connection actions for a plan after partial failure or a rollback request. Only newly created items can be reverted, not node deletions or parameter changes.

Instructions

把某个计划已经做过的建节点/连线动作撤销掉。执行到一半失败、或者用户说「撤了重来」时用。注意：删除节点和改参数无法撤销，只有新建的能撤。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan_id": "<plan_id>"
    },
    "name": "duddy_rollback_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the critical limitation: only newly created nodes/edges can be rolled back, while deletions and parameter changes cannot be undone. It omits what happens to plan state after rollback and the return behavior, keeping it short of 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 tight sentences: action first, then when-to-use, then the key caveat. Every sentence earns its place with no redundancy.

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

Completeness4/5

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

For a single-parameter mutation tool with no annotations or output schema, the description covers purpose, trigger conditions, and the main behavioral limit. It could say more about post-rollback plan state, but is largely complete for correct invocation.

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?

Only one parameter (plan_id) with 0% schema description coverage. The description implies plan_id identifies the plan to roll back but adds no format or sourcing detail beyond that inference, so it only marginally compensates for the coverage gap.

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 (rollback/undo) and resource (a plan's already-executed node/edge creation actions), and scopes it precisely to newly created items. An agent can distinguish this from duddy_abort_plan or duddy_apply_step without opening any schema.

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?

Gives explicit when-to-use triggers: mid-execution failure or a user request to 'undo and redo'. It does not name a sibling alternative (e.g., abort_plan) for contrast, but the usage context is clear.

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