Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

reactivate_model_key

Destructive

Reactivate an existing unmanaged Failed key index after correcting its cause, preserving key columns and avoiding key recreation or deletion. Preview with planHash, then submit explicitly.

Instructions

Preview/submit the native ReactivateEntityKey Action only for an existing unmanaged Failed key index after its cause has been corrected. Uses actual key LogicalName, preserves key columns and never recreates/deletes the key. Requires planHash and explicit unprotected Action. Acceptance is separate from a new job link and Active state; performs one metadata readback, never polls/replays the submission. Inspect later with get_model_key.

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true performs reads/eligibility checks and returns a native request preview. Set false to execute.
dry_runNoDefault true performs reads/eligibility checks and returns a native request preview. Set false to execute.
schemaNameNo
logicalNameNo
schema_nameNo
expectedHashNoCurrent preview planHash (binds target, patch and environment), required for execution.
logical_nameNo
expected_hashNoCurrent preview planHash (binds target, patch and environment), required for execution.
solutionUniqueNameNoExisting unmanaged solution; its publisher prefix is validated for new schemas.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
solution_unique_nameNoExisting unmanaged solution; its publisher prefix is validated for new schemas.
allowUnprotectedWriteNoExplicitly permit the native PUT/Action without atomic concurrency protection. A preview fingerprint is still required.
allow_unprotected_writeNoExplicitly permit the native PUT/Action without atomic concurrency protection. A preview fingerprint is still required.

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

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

Adds substantial behavior beyond the annotations: it clarifies the key is never recreated or deleted and key columns are preserved, that acceptance is distinct from a new job link and Active state, that only one metadata readback occurs, and that it never polls or replays the submission. The preview-vs-submit split is also spelled out, which materially reframes the destructive/idempotent hints without contradicting them.

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?

Front-loaded with the action and eligibility constraint, then prerequisites, then semantics, then the follow-up tool. It is dense with domain jargon and slightly run-on in the acceptance sentence, but every clause carries information.

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?

Covers the eligibility gate, the preview/execute contract, safety behavior, and the meaning of a successful acceptance, which is the right level of detail for a stateful mutation with no output schema. What a preview response actually contains and the role of environment_profile remain unstated, a minor gap.

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?

With 69% schema coverage, the description adds real meaning to the gating parameters: planHash (expectedHash) is required for execution, allowUnprotectedWrite must be explicit, and the key LogicalName is the actual name rather than a display name. Less is said about solution_unique_name's publisher-prefix role and the optional environment_profile, which the schema already partly covers.

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?

States a specific verb and resource ('ReactivateEntityKey Action' on an existing unmanaged Failed key index) and bounds the scope tightly ('only for ... Failed key index after its cause has been corrected'). This clearly separates it from create_model_key and get_model_key, which the description also names.

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?

Gives a strong precondition chain: only for Failed keys, only after the cause is corrected, and requires planHash plus an explicit unprotected Action. It also routes post-hoc inspection to get_model_key. It does not explicitly name what to use instead when the key is not in a Failed state, so it stops just short of full alternative routing.

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