Skip to main content
Glama

source_validate

Read-only

Validates XML well-formedness, Dynamics artifact identity, and lexical X++ structure to catch malformed source before edits or builds.

Instructions

Validate XML well-formedness, Dynamics artifact identity, and lexical X++ structure.

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": {
      "path": "<path>"
    },
    "name": "source_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo

Output Schema

NameRequiredDescriptionDefault
okYes
kindNo
pathNo
rootNo
errorNo
validNo
sha256No
newlineNo
artifactNo
encodingNo
referencesNo
diagnosticsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that validation spans three distinct layers (XML, artifact identity, X++ lexical structure), but does not say how failures are reported or whether validation stops at the first failure. The presence of an output schema reduces the need to describe return values.

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?

A single front-loaded sentence with no filler; the three validation facets are enumerated cleanly. It is efficient, though its terseness leaves key details unstated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Enough to know this is a read-only validator of the file at a path, and the output schema covers results. However, with two undocumented parameters, no schema descriptions, and a sibling named artifact_validate, the definition leaves real ambiguity about invocation and tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions either parameter. "path" is inferable, but "root" is completely unexplained — an agent cannot tell whether it is a root element name, a workspace root, or a scope filter — so the description fails to compensate for the coverage gap.

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") plus three concrete facets: XML well-formedness, Dynamics artifact identity, and lexical X++ structure. That is far better than a tautology, but it gives no differentiation from the sibling artifact_validate, whose name suggests overlapping artifact validation, leaving ambiguity about which validator to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no named alternative. Nothing tells an agent whether to run this before source_write, instead of source_parse, or alongside artifact_validate.

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