Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

update_existing_record

Destructive

Updates an existing Dataverse record with ETag/row-version protection, blocking writes when concurrency is unsupported unless unprotected writes are explicitly allowed. Does not upsert missing GUIDs.

Instructions

Update a native record with row-version protection where supported. Defaults to a fresh ETag; unsupported concurrency stops writes unless unprotected operation is explicit. Does not upsert a missing GUID.

Input Schema

NameRequiredDescriptionDefault
idYes
dataYesNative JSON attribute data. Related bindings must stay inside the configured organization API. Local JSON limit 10 MiB.
dryRunNoCompatibility alias for dry_run. Conflicting aliases are rejected.
dry_runNoRead-only preview of environment, target, changes and write blockers. Default false; sensitive fields are masked.
ifMatchNoCompatibility alias for if_match. Conflicting aliases are rejected.
if_matchNoSpecific ETag from a prior read/preview. Without it, reads the current record ETag when the table supports concurrency.
collectionNameNoCompatibility alias for collection_name. Conflicting aliases are rejected.
collection_nameNoNative EntitySetName, such as accounts. Validated against table metadata.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
allowUnprotectedWriteNoCompatibility alias for allow_unprotected_write. Conflicting aliases are rejected.
allow_unprotected_writeNoDefault false. Explicitly allow an unprotected write if table concurrency is unconfirmed, or for collection relationship membership. 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

A3.7/5.0
Behavior4/5

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

Beyond the destructive/not-idempotent annotations, the description discloses the concurrency failure mode, the default ETag acquisition strategy, and that a missing GUID will not be created. It does not say whether the supplied 'data' object merges with or replaces existing attributes, which is the main remaining behavioral ambiguity for a destructive update.

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?

Three tight sentences with the primary action front-loaded and each sentence carrying a distinct constraint (concurrency, unsafe-write gate, no-upsert). No filler or repetition, though the phrasing is dense enough that a little structure would aid scanning.

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 an 11-parameter destructive mutation with 91% schema coverage and no output schema, the description covers the concurrency contract and the create-vs-update boundary well. The notable gap is update semantics for the 'data' object (merge vs replace) and a pointer to dry_run as the safe preview path, which the schema documents but the description never connects.

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 91%, so the schema already explains id, data, if_match, allow_unprotected_write, and the aliases, making baseline 3 correct. The description restates the if_match/default-ETag behavior with a small amount of added linkage to the unprotected-write flag, but adds no syntax or format detail beyond 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?

States a specific verb and resource ('Update a native record') and adds a distinguishing scope note ('Does not upsert a missing GUID'), which implicitly separates it from upsert_record_by_key. The row-version protection clause further narrows what kind of update this is, so an agent can identify it without opening the schema.

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?

Gives one conditional rule (writes stop when concurrency is unsupported unless allow_unprotected_write is explicit) which is useful operational guidance. However, it never explicitly routes the agent to alternatives such as create_new_record, upsert_record_by_key, or the dry-run preview path, so alternative selection is largely left to inference.

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