Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

d365_plugin_assembly_update

Destructive

Update a stored Dynamics 365 plugin assembly DLL while preserving existing plugin type IDs and names; use preview-first validation before saving.

Instructions

Default preview only. Compare actual DLL against a stored unmanaged database assembly and preserve all existing plugin type IDs/names. Permit same major/minor non-decreasing build/revision, same identity/framework/references and AnyCPU signed managed DLL only. Managed, packaged, workflow, added/removed/unresolved types and dependency changes are blocked. Execute with preview fingerprint and metadata-gated concurrency; verify stored bytes, identity and type IDs after saving. .NET 10 Runtime required. Never creates assemblies or retargets steps.

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true; use false only with the same preview fingerprint.
dry_runNoDefault true; use false only with the same preview fingerprint.
ifMatchNoSpecific ETag; wildcard rejected.
filePathNoLocal regular managed DLL, at most 16 MiB. Never executed.
if_matchNoSpecific ETag; wildcard rejected.
file_pathNoLocal regular managed DLL, at most 16 MiB. Never executed.
assemblyIdNo
assembly_idNo
contentBase64NoCanonical base64 managed DLL; exclusive with file_path.
content_base64NoCanonical base64 managed DLL; exclusive with file_path.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
expectedFingerprintNo
expected_fingerprintNo
allowUnprotectedUpdateNoExplicitly allow If-Match:* only when table concurrency is not confirmed; cannot bypass a supplied ETag.
allow_unprotected_updateNoExplicitly allow If-Match:* only when table concurrency is not confirmed; cannot bypass a supplied ETag.

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
Behavior5/5

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

Annotations only flag destructive/non-idempotent; the description goes far beyond them by enumerating the exact accepted version transitions, the DLL constraints (AnyCPU, signed, managed, same identity/framework/references), the change classes that are blocked, the fingerprint/concurrency gating, and post-save verification of bytes, identity and type IDs. Nothing here contradicts destructiveHint=true — the preview-first default is consistent with it.

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?

Nearly every clause carries information, but the front-loading is poor: the first sentence is a preview-mode default rather than what the tool does, and the constraint inventory runs together as dense fragments without grouping. A short leading statement of purpose would let the remaining sentences land as conditions.

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 15-parameter mutation with no output schema, the description covers the prerequisites (.NET 10 runtime), the accepted inputs, the failure conditions, and the fact that the result should be verified afterwards. It stops short of stating required permissions or what the response body contains, which matters for a tool with no declared output schema.

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 73%, so most parameters already carry their own meaning, but assembly_id and environment_profile are undocumented in both places, and the camelCase/snake_case alias duplication is never explained. The description does add real semantics for expectedFingerprint and ETag-gated concurrency, and constrains what file_path/content_base64 may contain, but it does so conceptually rather than per 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 text makes clear this operation replaces the stored DLL of an existing unmanaged database assembly in place while preserving plugin type IDs/names, and 'Never creates assemblies or retargets steps' distinguishes it from a creation tool. It never states the verb+object plainly ('update the assembly DLL'), opening instead with a preview-mode note, so the agent must infer the core action from the name plus constraints.

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?

'Default preview only' plus 'Execute with preview fingerprint' gives a preview-then-execute workflow, and the blocked-change list tells the agent when this call will fail. However, no sibling is named (e.g. d365_plugin_assembly_inspect for read-only inspection, or a create path when no assembly exists), so tool selection is only implied.

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