Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_solution_component_dependencies

Read-only

Retrieves required, dependent, or delete dependencies for a Dataverse solution component after CSDL validation and returns projected dependency edges with explicit completeness bounds.

Instructions

Invoke native RetrieveRequiredComponents, RetrieveDependentComponents or RetrieveDependenciesForDelete after current CSDL validation. Default direction required. Returns projected dependency edges and explicit bounded completeness. Does not compute transitive closure, authorize deletion or prove deployment readiness.

Input Schema

NameRequiredDescriptionDefault
topNoMaximum returned rows, default 500; completeness is explicit.
maxPagesNoMaximum native pages, default 5.
directionNo
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
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

A4/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation it discloses that results are bounded (explicit completeness flag, page caps) and that the graph is non-transitive, which matters for correct interpretation. It does not describe auth requirements or the concrete shape of a dependency edge, keeping it short of a 5.

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?

Four tight sentences with the capability, the default, the return contract and the exclusions, in that order. Some phrasing ('after current CSDL validation', 'projected dependency edges') is compressed to the point of opacity but nothing is redundant.

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 9-parameter read tool with no output schema and only a readOnlyHint annotation, the definition covers the tricky parts: which direction to choose, that completeness is bounded, and which adjacent questions it cannot answer. Only the return payload's structure remains underspecified.

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

Parameters4/5

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

Schema coverage is 67%, and the description supplies the missing semantic for the undescribed direction enum by tying each mode to a distinct native retrieve message, plus stating that direction defaults to required. It adds no per-parameter detail for top/maxPages, but the schema already documents those.

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 names a specific resource (dependency edges for a solution component) and maps it to three concrete native operations (RetrieveRequiredComponents, RetrieveDependentComponents, RetrieveDependenciesForDelete). It is jargon-dense and never says 'solution component' in plain terms, but an agent can still tell what is returned and how it differs from verify_solution_deployment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Boundaries are drawn explicitly on the negative side: no transitive closure, no deletion authorization, no deployment readiness proof, which steers the agent toward verify_solution_deployment for go/no-go checks. What is missing is a positive statement of when to pick this tool (e.g. before removing a component) and no sibling is named directly.

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