Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

d365_plugin_image_delete

Destructive

Preview and delete an unmanaged customizable image by exact ID using a preview fingerprint and concurrency checks, then confirm deletion with a 404 response without removing the parent step.

Instructions

Preview/delete an unmanaged customizable image by exact ID. Requires preview fingerprint, metadata-gated concurrency and a subsequent 404 to confirm deletion. Does not delete its parent step or retry a write.

Input Schema

NameRequiredDescriptionDefault
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, and the description adds real context beyond that: fingerprint-gated two-phase execution, metadata-gated concurrency, and 404 as the confirmation signal. The trailing 'or retry a write' is vague, keeping it below 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?

Three dense sentences with the core operation front-loaded and no filler. The final clause is terse to the point of ambiguity, but the structure is efficient.

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, 11-parameter tool with no output schema, the description covers the preview/confirm cycle, concurrency gating, and the blast radius (parent step untouched). It omits required permissions and environment_profile usage, but the operational essentials are present.

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 82%, so the schema already explains dryRun, ifMatch, expectedFingerprint, and allowUnprotectedUpdate. The description only loosely maps to those fields ('preview fingerprint', 'metadata-gated concurrency') without adding format or constraint detail beyond the schema.

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 (preview/delete an unmanaged customizable image) scoped to an exact ID, which cleanly separates it from the register/update/query plugin-image siblings. It does not explicitly name a sibling alternative, so it falls just short of a 5.

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 description implies a preview-first workflow via 'Requires preview fingerprint' and clarifies a scope boundary ('Does not delete its parent step'), but it never states when to choose this tool over d365_plugin_image_update or when deletion is inappropriate. Usage is inferable rather than explicit.

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