Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

edit_model_view

Destructive

Edit a public system view to add or remove display columns, set widths, or reorder root fields while preserving filters, joins, and FetchXML dependencies.

Instructions

Structurally edit a public system view: add/remove root display columns, set widths or replace simple root-field ordering. Preserves filters, joins and FetchXML attributes needed by other dependencies. Rejects aggregate/distinct query rewrites. Default preview, fingerprint and metadata-gated ETag/fallback checks, saved readback, no automatic publish.

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

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

Beyond the annotations, it discloses important behavior: filters, joins, and FetchXML attributes needed by dependencies are preserved; unsupported aggregate/distinct rewrites are rejected; preview is the default; fingerprint/ETag checks gate execution; saved readback occurs; and no publish happens automatically. These are substantive operational traits for a destructive mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded: purpose first, then preservation guarantees, exclusions, and execution safety behavior. Every clause adds useful information and there is no filler or repetition.

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 a complex destructive mutation tool with 15 parameters and no output schema, the description covers the main purpose, constraints, preservation behavior, preview default, concurrency checks, readback, and publish boundary. It leaves some operational details such as permissions and the unprotected-write bypass implicit, but is otherwise sufficiently complete.

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?

With only 33% schema description coverage, the description adds important meaning by mapping `operations` to add/remove column, width, and simple order changes, and by explaining preview behavior plus fingerprint/ETag checks. It does not fully explain every parameter, notably `allow_unprotected_write` and `environment_profile`, but the schemas for those are somewhat self-contained.

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?

The description uses a specific verb and resource: structurally edit a public system view. It enumerates the exact supported edits (add/remove root display columns, set widths, replace simple root-field ordering), so an agent can distinguish this from broader model, form, or record editing tools.

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?

The description establishes clear usage context and gives an explicit when-not constraint: aggregate/distinct query rewrites are rejected. It also clarifies that this is a structural view-edit operation with preview by default and no automatic publish, though it does not name a specific sibling alternative to use instead.

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