Skip to main content
Glama

validate_assembly

Validates assembly.xml and assembly-diagram.xml against Studio-specific rules, catching broken routes, missing required attributes, and stale diagram references before opening in Workday Studio.

Instructions

Validates assembly.xml (and assembly-diagram.xml if present) against Studio-specific rules.

assembly.xml checks: ERROR — XML comments present (shifts @mixed indices, breaks diagram connections) ERROR — Broken routes-to / routes-response-to (target id does not exist) ERROR — cc:workday-out-soap missing application= or version= ERROR — cc:workday-out-soap used for RAAS (must use cc:workday-out-rest) ERROR — cc:workday-out-rest missing extra-path= ERROR — cc:http-out missing endpoint= ERROR — cc:xslt-plus missing url= WARNING — vm:// endpoint references a local-in id that does not exist WARNING — url= references an XSL file not found in WSAR-INF INFO — TODO stubs still present (sub-flows not yet filled in)

assembly-diagram.xml checks (when diagram file exists): ERROR — diagram href="assembly.xml#Id" points to an id no longer in assembly.xml (stale reference from a rename or delete — causes scala.MatchError on open) WARNING — renderable assembly element has no diagram entry (missing from visualProperties)

Run this after update_sub_flow, any manual assembly edit, or any component rename/delete. Fix all ERRORs before opening in Studio. WARNINGs block testing, not diagram load.

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": "validate_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_nameYesProject name, e.g. "INT145_My_Integration"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does an excellent job of disclosing failure semantics — severity tiers, the concrete consequence of stale diagram hrefs (scala.MatchError on open), and which severities block what. A 5 would require stating that this is a read-only check that reports rather than repairs and roughly what the report contains, which it never does.

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 a one-sentence purpose followed by a scannable severity-tagged checklist, and the closing lines tell the agent how to prioritize findings. The enumeration is long but each line is an actionable diagnostic rather than filler, though the grouping could be tighter.

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 one-parameter validation tool with no output schema, the description covers what is checked, what severity each finding carries, and the operational consequences. The main remaining gap is the shape of the returned report — whether findings include file paths, line numbers, or counts — which the agent would need in order to act on results programmatically.

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?

There is a single required parameter, project_name, and schema description coverage is 100%, so the schema already explains it. The description adds no naming conventions, path resolution behavior, or defaulting rules beyond what the schema provides; baseline 3 applies.

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 opening line names a specific verb ("Validates") and concrete resources (assembly.xml and assembly-diagram.xml), and the enumerated check list makes the scope unmistakable. It does not, however, differentiate itself from the sibling validate_xml_file, so an agent must infer that this one is the Studio-rule-specific validator rather than geneeric XML well-formedness.

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 trigger conditions: "Run this after update_sub_flow, any manual assembly edit, or any component rename/delete." It also tells the agent how to act on results — "Fix all ERRORs before opening in Studio" and that WARNINGs block testing but not diagram load. No explicit when-not or named alternative (validate_xml_file) is offered.

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