Skip to main content
Glama

analyze_peci_output

Inspect a sample Workday PECI/PICOF XML file before writing or changing XSLT to detect connector type, namespace, worker/change counts, element paths, and ready-to-use XPath while masking PII.

Instructions

Inventory a sample Workday PECI or PICOF output XML file (downloaded from an integration event and saved in the project) before writing or changing its XSLT.

Returns: detected connector type and namespace, worker and effective-change counts, event code distribution, and every element path with its occurrence count, change-flag counts (isAdded / isUpdated / isDeleted / priorValue) and a ready-to-use XPath relative to peci:Effective_Change or peci:Worker — feed those straight into create_peci_transform.

Values are MASKED by default because these files contain employee PII. Set show_sample_values=true only for test-tenant data.

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_path": "<file_path>"
    },
    "name": "analyze_peci_output"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath of the sample file relative to the project root, e.g. "samples/peci_output.xml"
max_pathsNoCap on element paths returned. Default 400.
max_file_mbNoRefuse files larger than this. Default 25 MB.
path_filterNoOnly return element paths containing this text (case-insensitive), e.g. "Compensation".
project_nameYesThe Studio project name
show_sample_valuesNoInclude one example value per path. Default false (masked). Use only with test data.

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 PII masking by default, the opt-in to reveal values, the ready-to-use XPath output relative to peci:Effective_Change / peci:Worker, and the size-guard behaviour. It never explicitly states the tool is read-only (implied by 'Inventory') and doesn't say what happens when max_paths truncates the result.

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 sentence, then a clearly labelled 'Returns:' block, then the masking warning. Slightly long, but each sentence carries distinct information an agent needs before calling.

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, so the description properly enumerates what comes back: connector type and namespace, worker and change counts, event code distribution, element paths with occurrence and change-flag counts, and XPaths. Only error/truncation reporting and the read-only nature are left unstated for a six-parameter 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 coverage is 100%, so every parameter already carries its own description; the description only reinforces the show_sample_values masking semantics. It adds no new meaning for file_path, max_paths, path_filter, or max_file_mb, so 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?

States a specific verb (Inventory) and resource (Workday PECI or PICOF output XML) plus the workflow context: read a downloaded sample before writing or changing its XSLT. It also names the concrete downstream consumer, create_peci_transform, so the agent can place it precisely among siblings.

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 timing guidance ('before writing or changing its XSLT') and a conditional rule for show_sample_values=true (test-tenant data only). It does not say when to prefer a sibling such as validate_xml_file instead, so the exclusions side is thin.

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