Skip to main content
Glama

validate_xml_file

Validates Workday Studio XML or XSLT files for well-formedness and returns parse errors with line and column numbers to pinpoint syntax issues.

Instructions

Validate an XML or XSLT file for well-formedness. Returns any parse errors with line/column numbers.

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

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to the file relative to the project root
project_nameYesThe Studio project name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that errors are returned with line/column numbers, but not whether validation happens on disk or in memory, whether success returns an empty result or a boolean, whether failures throw or are returned as data, or whether any permissions/project state are required.

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 short sentences with zero filler, and the purpose is front-loaded ahead of the return-value detail. Nothing in the text is redundant.

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 simple two-parameter validation tool, the description covers the core action and hints at the response shape (parse errors with line/column). The main remaining gap is the success-case result and the error/exception channel, which matter for a validator.

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%, with both project_name and file_path documented in the schema itself, so the baseline is 3. The description adds no additional meaning about path resolution or how project_name scopes the lookup.

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?

States a specific verb (validate), a specific resource (XML or XSLT file), and a precise criterion (well-formedness), plus what it produces. It implicitly distinguishes itself from validate_assembly by resource type, but never explicitly separates the two.

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?

The scope 'XML or XSLT file' gives a light routing criterion - use it on markup files, not on assemblies or other artifacts. However, there is no explicit when-to-use statement, no prerequisites (e.g. that the project and file must exist), and no named alternative.

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