Skip to main content
Glama

artifact_validate

Read-only

Validates a supported artifact's XML, X++, registry shape, identity, filename, and companion metadata to catch inconsistencies before editing or building Dynamics 365 Finance and Operations files.

Instructions

Validate a supported artifact's XML, X++, registry shape, identity, filename, and companion metadata.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo

Output Schema

NameRequiredDescriptionDefault
okYes
kindNo
pathNo
rootNo
errorNo
validNo
sha256No
newlineNo
artifactNo
encodingNo
registryNo
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 safe, local, non-mutating profile is established without the description. The description adds real value by listing the six validation dimensions, which tells the agent this is a composite lint of syntax and metadata rather than a single-format parse. It does not disclose severity semantics or whether validation halts on first error, though an output schema exists that may carry that.

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 the action first and the checked dimensions following. No filler, no repetition of the tool name. Tight and scannable, though the enumeration is comma-dense enough to read as a list dump.

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?

The presence of an output schema excuses the description from explaining return values, and the low parameter count keeps the surface simple. What remains missing is material: the definition of "supported artifact" and the role of "root" with zero schema coverage leave real ambiguity about correct invocation.

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%, so the description carries the full burden for both parameters and says nothing about them. "path" is at least inferable from the enumeration of artifact aspects, but "root" is never mentioned and its meaning is completely opaque from both schema and description.

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") against a specific resource ("a supported artifact") and enumerates the dimensions checked: XML, X++, registry shape, identity, filename, companion metadata. That is far more informative than a tautology. It stops short of differentiating from the sibling source_validate, so an agent cannot tell from this text which validator applies to which input.

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 reference to alternatives such as source_validate, artifact_build, or artifact_design. The qualifier "supported artifact" is undefined, so an agent has no way to know whether a given file qualifies before calling.

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