Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

d365_plugin_image_update

Destructive

Preview and update an unmanaged Dynamics 365 plugin image, preserving omitted fields and enforcing fingerprint and concurrency checks before reading back the saved values.

Instructions

Preview/update an unmanaged customizable image. Omitted patch values are preserved. Checks fields, parent step and duplicate aliases, requires preview fingerprint and metadata-gated concurrency, then reads back saved fields.

Input Schema

NameRequiredDescriptionDefault
patchNo
dryRunNoDefault true. Preview first, then use false with expected_fingerprint.
dry_runNoDefault true. Preview first, then use false with expected_fingerprint.
ifMatchNoSpecific image ETag; wildcard rejected. Defaults to the current ETag when concurrency is supported.
imageIdNo
if_matchNoSpecific image ETag; wildcard rejected. Defaults to the current ETag when concurrency is supported.
image_idNo
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
expectedFingerprintNoFingerprint from the same operation preview, required for actual writes.
expected_fingerprintNoFingerprint from the same operation preview, required for actual writes.
allowUnprotectedUpdateNoExplicit opt-in to If-Match:* only when concurrency metadata is false/unknown and no specific ETag was supplied.
allow_unprotected_updateNoExplicit opt-in to If-Match:* only when concurrency metadata is false/unknown and no specific ETag was supplied.

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 flag destructiveHint=true and idempotentHint=false, so the bar is lower, and the description still adds real substance: omitted patch values are preserved (merge, not replace), fields/parent step/duplicate aliases are validated, a preview fingerprint is mandatory for writes, concurrency is metadata-gated, and saved fields are read back. That is meaningful operational detail not present in structured fields.

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 compact sentences, front-loaded with the core verb and the partial-update rule before the validation/concurrency mechanics. Dense but every clause carries information; no filler.

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, concurrency-sensitive mutation with no output schema, the description covers the preview/commit cycle, fingerprint requirement, validation performed, preservation semantics and read-back. An agent could call this correctly from the description plus schema; only sibling routing is thin.

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 75% with descriptions on dryRun, ifMatch, expectedFingerprint and allowUnprotectedUpdate, so much is already documented. The description contributes the important partial-update rule ('omitted patch values are preserved'), which shapes how the agent fills the nested patch object, but adds little else on the remaining parameters.

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 ('Preview/update an unmanaged customizable image') and its preview-vs-commit duality, which separates it from siblings like d365_plugin_image_register and d365_plugin_image_delete. It is clear what the tool operates on, though it never explicitly names those siblings.

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?

The preview-first workflow is strongly implied ('requires preview fingerprint'), and the schema's dryRun description spells out the two-step pattern. However, the description never states when to use this versus register/delete on the same image resource, leaving some inference to the agent.

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