Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

publish_model_table

Destructive

Publishes an entire Dataverse table, including other pending fields, forms, views and ribbon customizations, with a default preview to check scope before execution.

Instructions

PublishXml for one entire table, including OTHER pending fields, forms, views and ribbon customizations. Default preview exposes scope; publication is separate from save. No automatic save replay on publication failure.

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.
logicalNameNo
logical_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

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotency, but the description adds the crucial blast-radius fact that publishing one table also publishes OTHER pending customizations, plus preview-by-default and no save replay on failure. It stops short of naming required privileges or failure recovery steps, so it is strong rather than exhaustive.

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?

Three short sentences, each earning its place: scope, then workflow default, then failure semantics. The key blast-radius warning is front-loaded immediately after the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent publish with no output schema, the description covers what changes, that a preview is the default return, and what does not happen on failure. The main residual gap is that it never states a table identifier is mandatory despite the schema's required-count reporting 0.

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?

At 60% schema description coverage, the description contributes almost nothing parameter-specific: 'Default preview' merely restates the dryRun/dry_run schema text, and the table identifier parameters (logical_name/logicalName aliases) are only implied by 'one entire table'. Baseline 3 is appropriate since 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?

States a specific verb and resource ('PublishXml for one entire table') and defines scope precisely, including the fact that pending fields, forms, views and ribbon customizations ride along. It implicitly distinguishes itself from narrow publishers like publish_model_choices or publish_ribbon_solution, but never names an alternative explicitly.

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?

The preview-default and 'publication is separate from save' notes imply a preview-then-execute workflow and that saving must happen elsewhere first, but the agent must infer this. There is no explicit when-to-use vs when-to-use-a-sibling statement or listing of prerequisites.

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