Skip to main content
Glama

add_assembly_step

Insert a new step into assembly.xml and optionally wire it after an existing step, automatically rewiring routes-to so the new step inherits the predecessor's routing.

Instructions

Insert a new step into assembly.xml. Optionally wire it after an existing step (updates the predecessor's routes-to automatically). The new step inherits the predecessor's original routes-to as its own routes-to.

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>",
      "step_id": "<step_id>",
      "step_type": "<step_type>"
    },
    "name": "add_assembly_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoStep-specific options. Common: xsl_file, url, method, xpath, href, endpoint, description, output_mimetype, extra_path, branches (JSON array). workday-out-soap: application, version. send-error/log-error: rethrow_error, level. xml-to-csv: separator, line_separator, write_header_line, format. csv-to-xml: separator, use_first_line_as_header, root_name, row_name, format.
step_idYesUnique ID for the new step (e.g. "TransformWorkerData")
routes_toNoOverride what this step routes to. If after_step_id is set, defaults to the predecessor's current routes-to.
step_typeYesThe cc: step type to add
project_nameYesThe Studio project name
after_step_idNoInsert after this existing step and rewire its routes-to. Omit to append before </cc:assembly>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.7/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 disclosure burden, and it does surface the non-obvious side effect: inserting after a step rewires that predecessor's routes-to and the new step inherits the original routes-to. It does not cover failure modes (duplicate step_id, missing after_step_id, invalid step_type/options), reversibility, or whether the file is validated afterward.

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 sentences, front-loaded with the action, then the optional wiring behavior, then the resulting routes-to state. Every sentence carries a distinct fact and nothing is padded.

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 mutation tool with no annotations and no output schema, the description covers the primary call pattern and the risky side effect that an agent most needs to know. Error/validation behavior and the response shape remain unstated, which is a modest but real gap.

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 goes slightly beyond by explaining the causal relationship between after_step_id and routes_to rather than just the parameters in isolation. However, the schema already states the same inheritance rule, so the added meaning is marginal rather than substantial.

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 concrete verb and resource ("Insert a new step into assembly.xml") and implies the append-vs-insert choice, which clearly separates it from delete_assembly_step and rename_steps. It stops short of naming any sibling explicitly, so sibling routing is inferred rather than stated.

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?

The description gives positional guidance ("Optionally wire it after an existing step" vs the schema's note to omit after_step_id in order to append), which is real when-to-use information. It offers no guidance on when to prefer this over update_sub_flow or rename_steps for modifying an existing step, nor any prerequisites such as the project/assembly needing to exist.

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