Skip to main content
Glama

create_xsl_transform

Scaffolds a blank XSLT 2.0 transform in a Workday Studio project’s ws/WSAR-INF directory, adding correct namespace declarations and an editable stub root template.

Instructions

Scaffold a new blank XSLT 2.0 transform file in a project's ws/WSAR-INF/ directory. Creates the file with the correct Workday namespace declarations and a stub root template ready to edit.

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

Input Schema

NameRequiredDescriptionDefault
file_nameYesFile name without path (e.g. "TransformWorkerData.xsl"). Will be placed in ws/WSAR-INF/.
descriptionNoA comment describing what this transform does. Included in the file header.
output_typeNoOutput method for the transform. Defaults to "xml".
project_nameYesThe Studio project name
input_namespaceNoPrimary input XML namespace to match. Defaults to urn:com.workday/bsvc (Workday SOAP).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does say what gets created (Workday namespace declarations, stub root template), but never states overwrite behavior when the file already exists, permission requirements, or what the call returns.

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?

Two sentences, front-loaded with action and destination, with little waste. 'Ready to edit' is mildly filler but harmless.

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 scaffolding tool with a fully described schema and no output schema, the description is nearly complete on what the artifact will contain. The only real omission is collision/error behavior, which an agent invoking a file creator would want.

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 all five parameters are already documented; baseline 3 applies. The description reinforces that the file lands in ws/WSAR-INF/ and that namespace defaults are Workday SOAP, but adds no syntax or format detail beyond the schema.

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 (Scaffold) plus resource (blank XSLT 2.0 transform file) and exact location (ws/WSAR-INF/), which distinguishes it from siblings create_peci_transform and write_integration_file.

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?

Usage is implied rather than explicit: 'blank' and 'stub ... ready to edit' signal a create-then-edit workflow, but there is no direct statement of when to pick this over create_peci_transform or write_integration_file.

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