Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

publish_model_choices

Destructive

Publish one shared global choice via native PublishXml, including pending changes, and preview the request by default before execution.

Instructions

Publish one entire shared global choice by native PublishXml; includes other pending changes to this global choice. Default preview. Local choices use the separate whole-table publish_model_table tool. Publication never replays a save and does not verify UI behavior.

Input Schema

NameRequiredDescriptionDefault
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.
globalChoiceNameNo
global_choice_nameNo
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

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description goes further by warning that publication 'includes other pending changes to this global choice' (collateral scope of the write) and that it 'never replays a save and does not verify UI behavior' (limits of validation). These are non-obvious side effects and caveats an agent could not derive from the structured fields.

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 short sentences, front-loaded with purpose then scope then the sibling routing then caveats; every sentence carries information. Minor telegraphic fragments ('Default preview') read tersely but do not obscure meaning.

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 destructive, non-idempotent mutation with no output schema, the description covers default mode, blast radius, and verification limits — the essentials. It omits permission/eligibility requirements and what the preview response contains, which leaves a small but real gap.

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 60%, with dryRun/dry_run and environment_profile already documented in the schema; the description's 'Default preview' mostly restates the dryRun default. The global choice name parameter (with its pattern and alias duplication) gets no added explanation of naming or alias behavior, so this sits at the baseline.

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 ('Publish one entire shared global choice') plus the mechanism ('by native PublishXml'), and explicitly separates itself from the sibling publish_model_table that handles local/whole-table choices. An agent can distinguish this from the other publish_* tools without opening any schema.

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?

Names the alternative explicitly ('Local choices use the separate whole-table publish_model_table tool') and states the default-safe mode ('Default preview'). It does not say when to prefer this over solution-level publishing (publish_appmodule, publish_sitemap), but for the choice-vs-table decision the routing is unambiguous.

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