Skip to main content
Glama

create_peci_transform

Generates an XSLT 2.0 transform that flattens Workday PECI or PICOF output into a delimited or fixed-width vendor file for payroll, benefits, and retirement feeds.

Instructions

Generate an XSLT 2.0 transform that flattens Workday PECI (or PICOF) output into a delimited or fixed-width vendor file, written to ws/WSAR-INF/ of a Studio project.

Use it for payroll, benefits, retirement or other vendor feeds built on the PECI/PICOF connectors. Call analyze_peci_output on a sample file first to discover the exact element paths and change flags in the tenant's output, then pass those paths as columns.

Handles: namespace declarations, RFC 4180 CSV quoting, any delimiter, header row, CRLF/LF, fixed-width padding and truncation, date re-formatting, first-non-blank fallback chains, constants, event-code filters (HIR, TERM, DTA...), and change-only rows (peci:isAdded / isUpdated / isDeleted flags).

See get_patterns topic "PECI and PICOF Output Transforms" for the design rules.

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

Input Schema

NameRequiredDescriptionDefault
sourceNoConnector output being transformed. Default "peci". Sets the default namespace.
columnsYesOutput columns in order.
delimiterNoField delimiter for csv output. Default ",". Use "|" for pipe or "\t" for tab.
file_nameYesXSLT file name, e.g. "PECI_To_Vendor_CSV.xsl". Placed in ws/WSAR-INF/.
overwriteNoReplace the file if it already exists. Default false.
quote_allNoQuote every csv field. Default false: quote only when needed.
row_scopeNoOne output row per peci:Effective_Change (default — change/event feeds) or one row per peci:Worker (current-state feeds).
descriptionNoWhat this transform produces, for the file header comment.
event_codesNoOnly emit rows whose peci:Derived_Event_Code is in this list (effective_change scope).
line_endingNoDefault "CRLF", which most payroll and benefits vendors expect.
changed_onlyNoOnly emit rows where something inside the row context carries an isAdded / isUpdated / isDeleted flag.
project_nameYesThe Studio project name
namespace_uriNoOverride the source namespace URI (default urn:com.workday/peci, or urn:com.workday/picof).
output_formatNoDefault "csv" (any delimiter).
include_headerNoWrite a header row. Default true for csv, false for fixed_width.
extra_namespacesNoAdditional prefix → URI declarations used in column XPaths (e.g. custom field namespaces).
exclude_event_codesNoSkip rows whose peci:Derived_Event_Code is in this list (effective_change scope).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the output location, that namespaces are declared, RFC 4180 quoting behaviour, line-ending defaults, truncation for fixed-width, and how isAdded/isUpdated/isDeleted flags drive change-only rows. It does not state what the tool returns or what happens when overwrite is false and the file already exists, which are the notable omissions.

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 purpose and the routing advice before any feature detail, and the paragraph breaks make it scannable. The "Handles:" enumeration largely restates capabilities already implied by the schema, so it is informative but partly redundant for an agent that reads the parameters.

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 17-parameter generator with nested column objects, no annotations and no output schema, the description supplies the conceptual model (row_scope semantics, change-flag filtering, fixed-width vs csv) an agent needs to build a valid call. Missing are the return value and the overwrite-collision behaviour, which matter for a file-writing tool.

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 17 parameters including the nested column object are already documented in structured form. The description's feature list (delimiters, header row, CRLF/LF, padding/truncation, date re-formatting, fallback chains, constants, event-code filters) maps onto those parameters but adds no syntax or format detail beyond them, so the baseline 3 applies.

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?

Names a specific verb and artifact ("Generate an XSLT 2.0 transform"), the source data (Workday PECI/PICOF output), the result (delimited or fixed-width vendor file) and where it lands (ws/WSAR-INF/). That level of specificity lets an agent separate it from generic siblings such as create_xsl_transform without opening any schema.

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 a clear applicability condition ("payroll, benefits, retirement or other vendor feeds built on the PECI/PICOF connectors") plus an explicit prerequisite workflow: run analyze_peci_output on a sample first, then pass the discovered paths as columns. It stops short of naming create_xsl_transform as the alternative for non-PECI transforms, so the boundary is implied rather than stated.

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