Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_model_ui_component

Read-only

Read a native unpublished form or view definition, including structural inventory, SHA-256 preview fingerprint, and native ETag, to inspect UI components without inferring publication state.

Instructions

Read a native unpublished system form/view definition, structural inventory, SHA-256 preview fingerprint and native ETag when available. Publication state is not inferred.

Input Schema

NameRequiredDescriptionDefault
idNo
kindNo
logicalNameNo
logical_nameNo
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / environment_profile
      Added value: +{
      +  "description": "Optional named environment profile for this call; omit to use the configured default.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_]{0,31}$",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes safety, and the description adds valuable behavioral context: it reads only unpublished native definitions and explicitly states that publication state is not inferred. It does not cover permissions, error behavior, or why publication state is excluded, but it goes meaningfully beyond the annotation.

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 dense sentence with no filler and front-loads the core purpose. It could be slightly more structured for readability, but every phrase contributes information.

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?

For a tool with five parameters at 20% schema coverage and no output schema, the description is incomplete. It lists returned artifacts and a publication caveat, but gives no guidance on parameter combinations, environment_profile usage, or when the returned fingerprint/ETag should matter.

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 20%, so the description should compensate for undocumented parameters, but it never mentions id, logical_name/logicalName, kind, or environment_profile. The agent must rely entirely on schema patterns and enums to understand how to select a form or view.

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 uses a specific verb, 'Read', and a precise resource, 'native unpublished system form/view definition', then lists the returned artifacts: structural inventory, SHA-256 preview fingerprint, and native ETag. It distinguishes itself from sibling tools like edit_model_form and edit_model_view by being read-only, though it does not explicitly name an alternative.

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 explicit guidance on when to use this tool versus list_model_ui_components, get_model_definition, or the edit variants. The phrase 'native unpublished' implies a context, but the agent must infer when that context applies and what prerequisites exist.

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