Skip to main content
Glama

list_assembly_steps

Parse a Workday Studio assembly.xml to list all integration steps with IDs, types, and routing, optionally including nested async-mediation and splitter steps, instead of reading the full file.

Instructions

Parse assembly.xml and return all steps with their IDs, types, and routing. Much faster than reading the full file when you just need to understand the integration flow.

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>"
    },
    "name": "list_assembly_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_nameYesThe Studio project name
include_nestedNoInclude steps nested inside cc:async-mediation and cc:splitter. Defaults to false (top-level only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose the read-only parsing nature, the returned fields, and a performance trait relative to full-file reads, but it says nothing about failure behavior (missing or malformed assembly.xml), whether the project must exist, or the default top-level-only scope.

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?

Two sentences, front-loaded with the core action and return shape, with the second sentence earning its place as a routing hint. No filler or 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?

There is no output schema, but the description compensates by naming the returned fields (IDs, types, routing). For a simple two-parameter read tool this is nearly complete; only error/missing-file behavior and the default nesting scope are left implicit.

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?

Schema description coverage is 100%, so both parameters including the include_nested default are already documented in the schema. The description adds nothing about parameter effects, so it sits at the baseline rather than earning more.

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?

The description gives a specific verb ('Parse assembly.xml') and a specific resource ('all steps') plus the exact fields returned (IDs, types, routing). It implicitly distinguishes itself from read_integration_file by noting it is 'much faster than reading the full file,' though it never names that sibling explicitly.

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 provides a clear usage condition — use this when you 'just need to understand the integration flow' — and contrasts it against the heavier alternative of reading the whole file. It stops short of saying when to prefer list_integration_params, get_workflow, or get_workspace_structure, which are plausible neighbors for flow understanding.

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