Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

inspect_form_node

Read-only

Reads a unique form subtree and its review hash from caller-supplied XML, letting you inspect a tab, section, or control node before validating or editing the form.

Instructions

Read a unique form subtree and its review hash from caller-supplied XML.

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": {
      "formxml": "<formxml>",
      "element": "<element>",
      "id": "<id>"
    },
    "name": "inspect_form_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
elementYes
formxmlYes
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

C2.9/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this is a safe read operation, so the bar is lower. The description adds that input is caller-supplied XML and that a review hash is returned, which is useful context beyond annotations, but it does not describe error behavior, validation of the XML, or what the returned subtree/hash look like.

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?

The description is a single tightly worded sentence, front-loaded with the verb and resource and free of filler. Terms like 'unique' and 'review hash' are not elaborated, but that is more a clarity gap than a structural or verbosity problem.

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

Completeness2/5

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

There is no output schema, and schema descriptions are sparse, so the description should explain return structure and parameter meaning more fully. It leaves an agent guessing about how id and element are interpreted and what exactly a 'review hash' represents in the result.

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 only 25%, so the description needs to compensate for undocumented parameters. It implies formxml is caller-supplied XML, but it does not explain the element enum values (tab/section/control), what id identifies, or the optional environment_profile parameter, leaving key required parameters opaque.

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 states a specific verb ('Read'), resource ('form subtree'), and adds 'review hash' and 'caller-supplied XML'. It distinguishes inspection from mutation siblings through 'Read', but it does not explicitly distinguish itself from close siblings like inspect_form_row or prepare_form_node_candidate.

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, and no alternatives are named. The only usage cue is the implied read-only inspection context from 'Read', leaving an agent to infer when this is preferable to inspect_form_row or prepare_form_node_candidate.

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

Deploy Server

Other Tools