Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

update_model_labels

Destructive

Update table and column display names, collection names, and descriptions in Dynamics 365 while preserving other metadata; preview by default, execute with hash and write permission.

Instructions

Update table/column labels by native full-definition PUT with MSCRM.MergeLabels=true. Preserves other retrieved properties, including choice definitions. Does not update option values: use change_model_choice_value. Execution requires current expected_hash and allow_unprotected_write=true; a concurrency race remains. Default preview.

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.
descriptionNo
displayNameNo
logicalNameNo
display_nameNo
expectedHashNo
logical_nameNo
attributeNameNo
expected_hashNo
attribute_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
displayCollectionNameNo
allow_unprotected_writeNo
display_collection_nameNo

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

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

Annotations already flag destructiveHint=true and idempotentHint=false; the description adds real value on top by saying other retrieved properties (including choice definitions) are preserved, that a concurrency race remains despite the hash guard, and that the default is a non-executing preview. It does not spell out what is irreversibly lost on a bad write or how the hash is obtained, which is the main remaining gap for a destructive tool.

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 operation and its mechanism, then the preservation guarantee, then the exclusion, then the execution preconditions. Dense but every clause carries information; only the mechanism detail (MergeLabels) is arguably over-specific for a selection decision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, 18-parameter mutation with no output schema, the description covers the safety-critical pieces (hash guard, unprotected-write flag, preview default, concurrency caveat). It is incomplete on how table-vs-column targeting works via logical_name/attribute_name and on the localized-label payloads, which an agent must infer from property names alone.

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 only 28% across 18 parameters, so the description has to compensate. It explains the semantics of expected_hash, allow_unprotected_write and the preview default, but says nothing about which of logical_name vs attribute_name selects a table versus a column, or about the displayName/description/displayCollectionName localization arrays and solution_unique_name.

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 ('Update table/column labels') plus the mechanism ('native full-definition PUT with MSCRM.MergeLabels=true'). It also carves out an explicit boundary against change_model_choice_value, so an agent can distinguish this from the option-value tool without opening schemas.

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 concrete when-not ('Does not update option values: use change_model_choice_value') and states the preconditions for execution (current expected_hash, allow_unprotected_write=true) with a preview default. It stops short of routing against other nearby mutators like update_model_column_settings or edit_model_view, so not a full when/when-not map.

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