Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

edit_model_form

Destructive

Structurally edits a Dynamics 365 Main form by appending a scalar field with a compatible control template, adding a verified JavaScript library, or binding onload, onsave, and onchange handlers.

Instructions

Structurally edit a Main form: append a scalar field using an explicit compatible existing control template, add a verified JavaScript library, or bind onload/onsave/onchange. No arbitrary XML, PCF/Lookup template copying or code execution. Default preview. Execute with current expected_hash; native ETag support is checked, otherwise explicit allow_unprotected_write is required. No automatic publication.

Input Schema

NameRequiredDescriptionDefault
idNo
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.
ifMatchNo
if_matchNo
operationsNo
logicalNameNo
expectedHashNo
logical_nameNo
expected_hashNo
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 the tool as destructive and non-idempotent; the description adds real context beyond them — optimistic concurrency via hash/ETag, the unprotected-write escape hatch, and the fact that nothing is published automatically. It stops short of describing what a failed hash match or partially applied operation list does, which would complete the destructive-operation 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?

Dense but front-loaded: what it edits, what it refuses to do, then the execution gating. Sentence fragments read tersely and a couple of clauses ('native ETag support is checked, otherwise...') require a second read, but nothing is redundant.

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 15-parameter, destructive, preview-first tool with no output schema, the description covers constraints and gating well but never describes what a preview or success response looks like, where the expected_hash comes from, or how to publish afterward. An agent can invoke it safely but cannot fully anticipate its result.

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 coverage is only 33%, and the description compensates for the important ones: expected_hash as the concurrency token, allow_unprotected_write as the fallback when no ETag exists, and the operation variants. It adds nothing about id, logical_name, solution_unique_name, environment_profile, or how if_match relates to expected_hash, leaving several safety-relevant parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Structurally edit a Main form') and enumerates the three allowed operation families (append scalar field via existing template, add verified JS library, bind onload/onsave/onchange). An agent knows exactly what this tool mutates and cannot confuse it with view/ribbon/sitemap edit siblings.

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 clear operational conditions: preview is the default, execution requires current expected_hash, and when native ETag is unavailable an explicit allow_unprotected_write is required. It also rules out arbitrary XML, PCF/Lookup template copying, and code execution, but it does not point to an alternative tool for those unsupported cases or state that a separate publish step must follow.

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