Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

change_model_choice_value

Destructive

Inserts a numeric option or updates labels/descriptions in unmanaged Dynamics 365 choices, including global shared choices; previews by default and requires safeguards to execute.

Instructions

Insert a numeric choice option or update existing option labels/description through native InsertOptionValue/UpdateOptionValue (MergeLabels=true). Unmanaged choices only. Explicitly address a global choice to change shared values. Default preview; execution needs current expected_hash and allow_unprotected_write=true. No delete, renumber, state/status mutation or automatic publish.

Input Schema

NameRequiredDescriptionDefault
labelNo
valueNo
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.
operationNo
descriptionNo
logicalNameNo
expectedHashNo
logical_nameNo
attributeNameNo
expected_hashNo
attribute_nameNo
globalChoiceNameNo
global_choice_nameNo
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.
allowUnprotectedWriteNo
allow_unprotected_writeNo

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.0
Behavior4/5

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

Annotations already flag this as non-read-only, non-idempotent, and destructive, yet the description adds real value beyond them: preview-by-default, the MergeLabels=true merge semantics, unmanaged-only scope, and the concurrency guard via expected_hash. It does not say what the preview payload contains or whether updates overwrite existing labels for other languages, which would have completed the picture.

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 primary action and followed by scope, prerequisites, then exclusions in roughly the order an agent needs them. Every sentence carries information, though the heavy parentheticals and dash-list of prohibitions make it slightly dense on first read.

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 19-parameter destructive mutation with no output schema, the description covers the essentials: what changes, what is forbidden, what gates execution, and the preview default. Remaining gaps are the preview response shape and how label/description arrays interact when merging existing localized text.

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?

Schema description coverage is only 26% across 19 parameters, so the description carries weight: it explains expected_hash as a freshness requirement, allow_unprotected_write as an execution gate, and the global_choice_name versus logical_name/attribute_name addressing modes that the schema only expresses structurally via oneOf. It leaves the label/description array shape, value ranges, and solution_unique_name semantics entirely to 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?

The description gives a precise verb+resource: inserts a numeric choice option or updates existing option labels/descriptions, and names the underlying native operations (InsertOptionValue/UpdateOptionValue with MergeLabels=true). It implicitly separates itself from definition-level siblings like create_model_choices, but never names any sibling tool, so an agent must infer the boundary rather than read it.

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?

It states clear preconditions (unmanaged choices only, current expected_hash plus allow_unprotected_write=true to execute) and explicit exclusions (no delete, renumber, state/status mutation, or automatic publish). It also tells the agent to address a global choice explicitly when shared values must change. The one gap is that no alternative tool is named for the excluded operations.

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