Skip to main content
Glama

source_read

Read-only

Reads a bounded .xml or .xpp source file and returns its encoding, newline style, and SHA-256 for safe inspection of Dynamics 365 X++ artifacts.

Instructions

Read a bounded .xml or .xpp source file with its encoding, newline style, and SHA-256.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo

Output Schema

NameRequiredDescriptionDefault
okYes
bomNo
kindNo
pathNo
sizeNo
errorNo
sha256No
contentNo
newlineNo
encodingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3.2/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 safety is covered. The description adds that reads are 'bounded' and that encoding, newline style, and SHA-256 accompany the content, but never states the bound's size or the failure behavior when exceeded, so a key constraint stays vague.

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. It is efficient, though it is arguably too terse for a tool with an undocumented second parameter.

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 returned metadata need not be spelled out, and the read-only nature is covered by annotations. However, with 0% schema description coverage and one of two parameters unexplained, the definition does not carry enough for confident 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% and the description only indirectly implies what 'path' means. The 'root' parameter is completely unaddressed in both schema and description, leaving an agent to guess whether it is a base directory, a resolution anchor, or something else.

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 (read) and resource (source file), plus scoping constraints (.xml/.xpp, bounded) and the metadata returned. It is clearly distinguishable from siblings like source_write or source_parse, though it does not name them explicitly.

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?

Usage is only implied: an agent can infer this is for fetching raw source text, while source_parse/source_validate handle analysis. There is no explicit when-to-use statement and no guidance on what to do when a file exceeds the unspecified bound.

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