Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

update_model_column_settings

Destructive

Updates settings for existing unmanaged custom columns in Dynamics 365/Dataverse—length, precision, required level, auditing, search, defaults, and date format—using a previewed, hash-bound write.

Instructions

Default preview of existing ordinary unmanaged custom column settings; nine supported base types. Allows length/range/precision expansion, requirement level, auditing/search managed values, Boolean/existing Picklist defaults and DateTime display format. Preserves full definition, labels, choices and date behavior. Rejects narrowing, primary/derived/calculated/rollup/autonumber columns and type/schema changes. Execute with preview planHash as expected_hash plus allow_unprotected_write=true; full native PUT then readback, no automatic publication.

Input Schema

NameRequiredDescriptionDefault
patchNo
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.
logicalNameNo
expectedHashNoCurrent preview planHash (binds target, patch and environment), required for execution.
logical_nameNo
attributeNameNo
expected_hashNoCurrent preview planHash (binds target, patch and environment), required for execution.
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.
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.2/5.0
Behavior5/5

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

Annotations mark this destructive and non-idempotent; the description goes well beyond that by explaining that dry-run is the default, that execution requires a preview planHash bound to target/patch/environment, that an explicit unprotected-write flag bypasses atomic concurrency protection, and that a native PUT plus readback occurs with no automatic publication. It also discloses what is preserved (definition, labels, choices, date behavior) versus what is rejected, which is exactly the mutating-tool context an agent needs.

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?

It is compact for a 14-parameter mutation tool and every clause carries information; no filler sentences. The structure is telegraphic and semicolon-chained, so a few statements ("nine supported base types" with no list, "ordinary") require re-reading, and the purpose statement is not placed first.

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?

Given a nested patch object, no output schema, and destructive annotations, the description supplies the decision-critical facts: default preview, hash binding, the unprotected-write opt-in, excluded column classes, and the absence of automatic publication. The main gap is that the nine supported base types are referenced but never enumerated, so an agent cannot self-check eligibility from the description alone.

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 coverage is 64%, and the description compensates by enumerating the meaningful patch knobs (length/range/precision expansion, requirement level, audit/search-managed flags, Boolean/existing Picklist defaults, DateTime display format) and by tying expected_hash and allow_unprotected_write to the execution flow. It doesn't explain the snake_case/camelCase aliasing or the solution publisher-prefix constraint, though the schema descriptions cover the latter.

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 conveys that this tool previews and then applies settings updates to existing custom columns, and it pins the scope ("existing ordinary unmanaged", "nine supported base types"). It never states the verb explicitly ('updates'), and it doesn't name a creating sibling like create_model_column, so the agent must infer the create-vs-update boundary from the tool name alone.

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?

Strong exclusion guidance: it rejects narrowing, primary/derived/calculated/rollup/autonumber columns, and type/schema changes, which tells the agent when not to call it. It also states the two-step flow (preview by default, execute with planHash plus allow_unprotected_write=true). What's missing is an explicit pointer to the alternative tool when the exclusion applies.

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