Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

add_solution_component

Destructive

Adds one existing component to an unmanaged Dynamics 365 solution after validating its type, dependencies, and membership; previews changes by default and requires a plan hash to execute.

Instructions

Default preview of adding one existing component to a visible ordinary unmanaged solution. Validates the actual object/type, current CSDL and complete visible membership/required-dependency baseline. Types: 1 Entity, 2 Attribute, 9 global Option Set, 10 Entity Relationship, 14 Entity Key, 26 Saved Query, 60 System Form, 61 Web Resource, 90–93 plugin types/assemblies/steps/images. Attribute/Key requires logical_name. Fixed AddRequiredComponents=false/DoNotIncludeSubcomponents=true; implicit parent shells may still be added. Execute with planHash plus explicit unprotected Action; reread membership and report observed deltas without claiming export completeness.

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true; no add Action is sent.
dry_runNoDefault true; no add Action is sent.
componentIdNoNative object/metadata GUID, NOT the solutioncomponent membership row GUID.
logicalNameNo
component_idNoNative object/metadata GUID, NOT the solutioncomponent membership row GUID.
expectedHashNoCurrent preview planHash, required to execute.
logical_nameNo
componentTypeNo
expected_hashNoCurrent preview planHash, required to execute.
component_typeNo
solutionUniqueNameNo
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
solution_unique_nameNo
allowUnprotectedWriteNoExplicitly accept the native Action concurrency window; no atomic solution/dependency lock is claimed.
allow_unprotected_writeNoExplicitly accept the native Action concurrency window; no atomic solution/dependency lock is claimed.

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

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

Beyond the destructive/non-idempotent annotations, it discloses real behavior: fixed AddRequiredComponents=false and DoNotIncludeSubcomponents=true, yet implicit parent shells may still be added, and the concurrency window is explicitly unprotected. It also warns that observed deltas must not be reported as export completeness, which is unusually candid for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The default-preview constraint and the component-type table are front-loaded, which is right. The middle of the description degenerates into a semicolon-separated run-on mixing validation behavior, fixed flags, and execution rules, which makes it harder to scan than it needs to be.

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 destructive, non-idempotent mutation with no output schema, the description covers what is validated, what gets implicitly created, how execution is gated, and what should be reported afterward. The main remaining gap is failure modes: what happens when validation fails or the hash is stale is left implicit.

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?

With 15 parameters and only 60% schema coverage, the description does real work by enumerating component type codes (1, 2, 9, 10, 14, 26, 60, 61, 90-93) that the schema leaves as a bare integer, and by noting that Attribute/Key require logical_name. It still says nothing about the alias pairs or the environment_profile parameter.

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 and resource: adding one existing component to a visible, ordinary, unmanaged solution, with preview as the default mode. It never names a sibling tool, so the agent must infer the boundary with list_solution_components or get_solution_component_dependencies on its own.

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?

It clearly separates preview from execution: run by default as a dry run, then execute only with planHash plus an explicit unprotected Action flag. It doesn't point at alternative or prerequisite tools (dependency inspection, component listing), so the surrounding workflow must be guessed.

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