Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

execute_record_transaction

Destructive

Executes up to 100 validated create, update, delete, upsert, associate, or disassociate operations in one native Dataverse $batch change set, with dry-run preview and commit status reporting.

Instructions

Execute up to 100 validated mutations in ONE native $batch change set, without chunking or fallback to individual writes. Reports committed false for confirmed rejection and unknown for transport/server ambiguity. Preflight reads are outside the transaction; arbitrary HTTP and Content-ID dependencies are not accepted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operations": "<operations>"
    },
    "name": "execute_record_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
operationsYes
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

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

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

Annotations declare destructive=true and idempotent=false, but the description goes well beyond them: it discloses the 100-mutation ceiling, that there is no chunking or fallback, and crucially the outcome semantics — 'committed false for confirmed rejection and unknown for transport/server ambiguity.' What is still missing is how partial failures within the change set are handled and whether operation order is preserved.

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?

Four tight sentences with the core capability front-loaded and the failure-semantics and constraint clauses following in a logical order. Dense but no filler; the only mild cost is that the constraints on reads and Content-ID arrive without framing context.

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 tool that can emit up to 100 mutations in a single call, important behavior is left unstated: ordering guarantees between operations in the change set, and whether the change set is all-or-nothing on rejection. The description covers scope and result reporting but not the execution model an agent needs before composing a large batch.

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 75% and the schema already documents operations, dry_run, and environment_profile in detail. The description adds little param-level meaning beyond reinforcing the 100-operation cap and stating that preflight reads fall outside the batch, so the schema carries most of the load.

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 names a specific verb and resource plus its mechanism: 'Execute up to 100 validated mutations in ONE native $batch change set, without chunking or fallback to individual writes.' That mechanism detail implicitly separates it from plain single-record writers, but the near-identical sibling execute_record_batch is never named, so an agent must infer which of the two batch tools to pick.

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?

Usage is only implied through constraints — 'Preflight reads are outside the transaction' and 'arbitrary HTTP and Content-ID dependencies are not accepted' tell the agent what cannot be sent, not when to choose this tool over execute_record_batch or the individual create/update/delete tools. There is no explicit when-to-use or when-not-to-use statement relative to alternatives.

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