Skip to main content
Glama

Edit workflow steps and branches

spur_edit_workflow
Destructive

Insert/update steps, change waits and branches, remove named steps, reorder, or rename a workflow. Unmentioned steps are retained. New IDs must start step_. Branch parent IDs must exist. Editing a live workflow requires confirmation. Activation is a separate tool.

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": {
      "workflow_id": "<workflow_id>"
    },
    "name": "spur_edit_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
confirmNoSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
descriptionNo
workflow_idYes
upsert_stepsNo
remove_step_idsNo
ordered_step_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description earns credit by adding semantics the annotations cannot convey: 'Unmentioned steps are retained' discloses patch-style merge behavior rather than full replace, and the confirmation rule for live workflows flags an approval gate. It stops short of saying what removal actually cascades to (e.g., child branch steps) or whether the operation is atomic, which would matter for a destructive, non-idempotent call.

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?

Five short sentences, each carrying a distinct fact — scope, retention semantics, ID constraint, branch constraint, confirmation gate, sibling routing — with no restatement of the name or filler. The operation list is front-loaded and the constraints follow in the order an agent would apply them.

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 destructive, non-idempotent mutation with 7 parameters, low schema coverage and no output schema, the description covers the critical decision points: partial-update behavior, ID validation, branch integrity, and approval. Gaps remain around the step `config` payload, the meaning of the type enum values, and what (if anything) the call reports back about applied changes.

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?

Schema description coverage is only 14% (essentially just the confirm field), so the description has to compensate, and it largely does: the verb list maps onto upsert_steps, remove_step_ids, ordered_step_ids and name, and the constraints 'new IDs must start step_' and 'branch parent IDs must exist' explain the id/parent_step_id fields. It leaves the config object, the step type enum, and the maxItems caps entirely to the schema, so some parameters remain undocumented in prose.

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?

The opening sentence names the exact mutation surface — insert/update steps, change waits and branches, remove named steps, reorder, rename — plus the resource (a workflow). It also pre-empts confusion with the activation sibling by stating 'Activation is a separate tool,' so an agent can distinguish it from spur_create_workflow and spur_set_workflow_active without opening a 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?

It gives a clear routing rule for activation ('a separate tool') and a precondition for live workflows ('requires confirmation'), which tells the agent when the call needs explicit user approval. It does not explicitly say when to prefer this over creating a new workflow or over spur_manage_workflow, so the alternative-routing story is partial rather than complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources