Skip to main content
Glama

source_parse

Read-only

Parses Dynamics 365 XML or X++ code to return artifact members, source references, and diagnostics, supporting code analysis and validation.

Instructions

Parse Dynamics XML or X++ source and return artifact members, source references, and diagnostics.

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_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo

Output Schema

NameRequiredDescriptionDefault
okYes
kindNo
pathNo
rootNo
errorNo
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 some context by listing what the parse yields, but it says nothing about failure behavior on malformed source, how diagnostics are surfaced, or how partial results are handled — the kind of information an agent needs for a parser.

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 verb and resources lead. It is perhaps too terse for the two undocumented parameters, but nothing in it is wasted.

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?

An output schema exists, so the description needn't explain the returned members/references/diagnostics in detail. However, for a tool with two entirely undescribed parameters and no usage context, the definition leaves material gaps an agent must fill by trial.

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% with two parameters, and the description does not mention either. It never explains what the required 'path' points at or what 'root' scopes or overrides, so an agent must guess whether 'root' is a namespace prefix, a filesystem base, or a model root.

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?

The description names a specific verb ('Parse') and concrete resources ('Dynamics XML or X++ source') and states what is produced (artifact members, source references, diagnostics). It does not distinguish this from close siblings such as source_validate or source_read, so it falls short of full sibling differentiation.

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 or when-not-to-use guidance at all. The agent is not told when to prefer this parser over source_validate, source_read, or reference_resolve, leaving the choice to inference from tool names alone.

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