Skip to main content
Glama

rename_steps

Atomically updates a Workday Studio step ID across assembly.xml and assembly-diagram.xml, preventing diagram-open MatchError crashes from partial renames.

Instructions

Atomically renames a step ID in BOTH assembly.xml AND assembly-diagram.xml.

WHY THIS EXISTS: Renaming an ID in only one file causes a scala.MatchError crash when Studio opens the diagram. This tool updates all references in a single operation:

assembly.xml — id="OldID", routes-to="OldID", routes-response-to="OldID", endpoint vm:// paths containing /OldID assembly-diagram.xml — all href="assembly.xml#OldID" forms (visualProperties, connections source/target, swimlane elements)

SAFE TO USE FOR: cc:async-mediation, cc:local-in, cc:local-out, cc:route, cc:splitter, cc:send-error, cc:workday-out-*, cc:http-out, cc:workday-in, and any other element with an id= attribute.

Creates backups of both files before writing. Runs validate_assembly after.

BATCH RENAMES: call once per ID — do not batch multiple renames into one call.

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": {
      "project_name": "<project_name>",
      "old_id": "<old_id>",
      "new_id": "<new_id>"
    },
    "name": "rename_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_idYesNew step ID, e.g. "SetTransactionProps" — use verb+object PascalCase
old_idYesThe existing step ID to rename, e.g. "AsyncMediation3"
dry_runNoIf true, return the planned replacements without writing any files
project_nameYesProject name, e.g. "INT999_Employee_Sync"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses atomicity, the crash motivation (scala.MatchError), that backups of both files are created before writing, and that validate_assembly runs afterward. It omits failure/rollback behavior, where backups are written, and what happens if new_id already exists — meaningful gaps for a mutation tool.

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?

Front-loaded with the core action in the first sentence, then cleanly sectioned into rationale, affected references, and constraints. The element-type catalogue is long but functional; a few lines could be trimmed without loss.

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?

Four parameters, no output schema, and no annotations — the description covers the destructive mechanics and post-write validation, which is what an agent most needs. It does not say what is returned (backup paths, validation output), leaving the response shape undefined.

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 coverage is 100% so the baseline is 3, and the description earns above that by explaining the scope of old_id/new_id substitution — id=, routes-to, routes-response-to, vm:// endpoint paths, and href='assembly.xml#OldID' forms. It adds no meaning for dry_run beyond the schema, which caps it at 4.

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 and resource ('Atomically renames a step ID') plus the exact two files touched, which no sibling name alone conveys. An agent can distinguish this from rename_file or write_integration_file immediately.

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?

The 'SAFE TO USE FOR' list gives a concrete positive selection rule (any element with an id= attribute), and the batch-rename note ('call once per ID — do not batch') is a real usage constraint. It stops short of naming an alternative tool or stating an explicit when-not-to-use case, so it is not a full 5.

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