Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

d365_plugin_step_update

Destructive

Update Dynamics 365 plugin steps by changing fields or setting, keeping, or clearing secure/unsecure configuration while preserving omitted values and enforcing ETag concurrency.

Instructions

Update one plugin step. Omitted fields/configuration are kept; configuration supports keep/set/clear. Uses table concurrency metadata and a specific ETag by default. Secure set creates a replacement row and binds it in the same PATCH as step changes; clear unbinds. Existing configuration rows are retained, never blindly deleted. Write/readback failures preserve phase evidence.

Input Schema

NameRequiredDescriptionDefault
patchNo
dryRunNoCompatibility alias for dry_run. Conflicting aliases are rejected.
stepIdNoCompatibility alias for step_id. Conflicting aliases are rejected.
dry_runNoRead-only preview of the environment, resolved target and changes. Configuration values are withheld. Default false.
ifMatchNoCompatibility alias for if_match. Conflicting aliases are rejected.
step_idNo
if_matchNoSpecific ETag, for example W/"123". If omitted, uses the current step ETag. Never accepts wildcard.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
secureConfigurationNoCompatibility alias for secure_configuration. Conflicting aliases are rejected.
secure_configurationNo
unsecureConfigurationNoCompatibility alias for unsecure_configuration. Conflicting aliases are rejected.
allowUnprotectedUpdateNoCompatibility alias for allow_unprotected_update. Conflicting aliases are rejected.
unsecure_configurationNo
allow_unprotected_updateNoDefault false. Explicitly allow an update with If-Match:* if table metadata does not confirm optimistic concurrency. Does not bypass a supplied ETag conflict.

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.3/5.0
Behavior5/5

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

Annotations already declare non-readonly, non-idempotent, and destructive behavior, but the description adds concrete operational detail: omitted values are retained, configuration supports keep/set/clear, ETag/concurrency defaults apply, secure set creates and binds a replacement row, clear unbinds, and failures preserve phase evidence. This substantially exceeds annotation coverage without contradicting it.

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?

The description front-loads the verb/resource and packs useful behavioral semantics into a few sentences with no obvious waste. It is dense with jargon such as "phase evidence" and the secure-configuration sentence is complex, but the structure remains 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, 14-parameter update with no output schema, the description covers retention, concurrency, secure configuration replacement/unbinding, and failure evidence well. It still leaves success return shape and permission expectations unstated, so it is rich but not fully complete.

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?

The description adds meaning beyond the schema for several complex parameters: omitted fields/configuration are kept, configuration keep/set/clear actions are explained operationally, ETag defaulting is clarified, and secure set/clear effects are described. With 71% schema coverage it does not cover every parameter, such as dry_run or allow_unprotected_update, but it materially improves understanding of the nested update semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence, "Update one plugin step," gives a specific verb and resource, cleanly distinguishing it from sibling step-registration and step-query tools. It is not tautological and an agent can identify the operation immediately.

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?

Usage is implied by "Update one plugin step" and by the omitted-fields/configuration behavior, but there is no explicit routing between this tool and siblings such as d365_plugin_step_register or d365_plugin_steps_query. It offers no when-not guidance or clear alternative selection criteria.

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