Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

list_model_ui_components

Read-only

Lists bounded saved or unpublished system forms and views for one table, returning IDs and types with explicit list limits. Use it to inspect model-driven UI components without XML fallback.

Instructions

List bounded native saved/unpublished system forms or views for one table. Returns IDs and types, with explicit list limits; no XML or automatic published-version fallback.

Input Schema

NameRequiredDescriptionDefault
topNo
kindNo
logicalNameNo
nameKeywordNo
logical_nameNo
name_keywordNo
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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral detail beyond that: it returns only IDs and types, list results are explicitly bounded, and there is no XML payload and no automatic fallback to published versions. The two negative guarantees are the most valuable part, though the exact limit is left to the schema.

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?

Two sentences with no filler, and the most decision-relevant facts (scope and the no-XML/no-fallback limitations) come first. The opening noun phrase is stacked with qualifiers, which slightly hurts readability without adding waste.

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?

It covers return shape at a high level ('IDs and types') and result bounds, which is adequate for a list tool with no output schema. Against a seven-parameter schema with very low description coverage, though, an agent still lacks guidance on name_keyword filtering and environment_profile selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, so the description is expected to carry weight. It does implicitly map to three parameters — 'for one table' (logical_name), 'forms or views' (kind), and 'explicit list limits' (top) — but name_keyword and environment_profile receive no mention, leaving the keyword-filtering and environment-targeting behavior unexplained.

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 (list) and resource (native saved/unpublished system forms or views for one table), which lets an agent separate it from get_model_ui_component and edit_model_view. The phrasing 'bounded native saved/unpublished system forms or views' is dense and requires domain familiarity, but the scope is genuinely specific rather than tautological.

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 context is implied rather than stated: the tool is for enumerating saved/unpublished components for a table, and the 'no XML or automatic published-version fallback' clause hints at when a different tool is needed. However, no sibling is named as the alternative for XML retrieval or published-version inspection, so the agent must infer the routing itself.

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