Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

list_solution_components

Read-only

List solution component membership rows for a specific Dynamics 365 solution, with optional component ID and type filters to inspect what is included.

Instructions

List visible solutioncomponent membership rows for an exact solution; objectid/type, membership row ID and root inclusion behavior are separate. Optional filters combine with the solution. No code/XML/configuration is read; completeness does not prove export payload contents.

Input Schema

NameRequiredDescriptionDefault
topNoMaximum returned rows, default 500; completeness is explicit.
maxPagesNoMaximum native pages, default 5.
max_pagesNoMaximum native pages, default 5.
componentIdNoNative object/metadata GUID, NOT the solutioncomponent membership row GUID.
component_idNoNative object/metadata GUID, NOT the solutioncomponent membership row GUID.
componentTypeNo
component_typeNo
solutionUniqueNameNo
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
solution_unique_nameNo

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description still earns credit for adding real behavioral context: only *visible* rows are returned, no code/XML/configuration is read, and completeness of the listing does not prove what an export payload would contain. Those caveats materially change how an agent should interpret an empty or short result. It does not describe pagination limits, though the schema documents top/maxPages defaults.

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?

Three compact sentences, front-loaded with the scope statement, then filters, then caveats. Every sentence carries information, but the phrase 'root inclusion behavior are separate' is dense to the point of ambiguity and costs a little readability.

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

Completeness4/5

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

For a read-only listing tool with no output schema and ten (largely aliased) parameters, the description covers scope, filter behavior, visibility, and the completeness caveat. Pagination and default limits are left entirely to the schema, which is acceptable but leaves the agent to discover that results are capped by default.

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 coverage is 60%, so the baseline is 3. The description reinforces that objectid and component type are separate concepts and that filters are combined with the solution constraint, which slightly clarifies the componentId/componentType pair whose type param has no schema description. It adds no detail on top, maxPages, or environment_profile, so it does not compensate for the remaining coverage gap.

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 and resource: 'List visible solutioncomponent membership rows for an exact solution.' The noun is precise but jargon-heavy, and the clause 'objectid/type, membership row ID and root inclusion behavior are separate' is opaque on first read. It is clearly not a payload/export tool, which separates it from siblings like inspect_solution_package or export_solution, but it never names those siblings 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?

'Optional filters combine with the solution' implies filters narrow the result set, and 'for an exact solution' implies an exact-name match is required rather than a pattern. However there is no explicit routing guidance such as when to prefer this over get_solution_component_dependencies or inspect_solution_package; the agent must infer the boundary from the negative scoping sentence.

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