Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

import_ribbon_solution

Destructive

Preview and import reviewed classic Ribbon edits into an existing unmanaged Dynamics 365 solution, validating exact candidate files and acknowledging whole-solution import.

Instructions

Preview first, then submit one native async import into an EXISTING ordinary unmanaged solution for reviewed classic Ribbon edits. Replay the structured edits and require exact candidate bytes; match organization/caller/table/publisher/version/complete visible membership and a fresh target export payload baseline. This is a WHOLE-SOLUTION import, including other unchanged components. Execute with current planHash, allow_unprotected_write and allow_full_solution_import. No upgrade/managed/override/automatic publish. Unknown acceptance retains client importJobId and is never replayed. Accepted responses yield a same-server-process provenance receipt for separate publication; receipt loss/restart is not permission to reimport.

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true. Read-only ExportSolution POST can occur during preflight; import/publish is not sent.
changesNo
dry_runNoDefault true. Read-only ExportSolution POST can occur during preflight; import/publish is not sent.
logicalNameNo
expectedHashNo
logical_nameNo
expected_hashNo
sourceFilePathNoAbsolute original unmanaged source ZIP path.
source_file_pathNoAbsolute original unmanaged source ZIP path.
candidateFilePathNoAbsolute candidate ZIP path produced from this source and the same structured edits on this server version.
candidate_file_pathNoAbsolute candidate ZIP path produced from this source and the same structured edits on this server version.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
allowUnprotectedWriteNoExplicitly accept the remaining platform concurrency window; no atomic package/table/pending-customization lock.
allowFullSolutionImportNoExplicitly acknowledge that native import applies the entire existing unmanaged package, not just Ribbon.
allow_unprotected_writeNoExplicitly accept the remaining platform concurrency window; no atomic package/table/pending-customization lock.
allow_full_solution_importNoExplicitly acknowledge that native import applies the entire existing unmanaged package, not just Ribbon.

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?

Beyond the destructive and non-idempotent annotations, the description discloses critical behavior: whole-solution scope, async execution, exact-byte matching, no automatic publish, no replay on unknown acceptance, and provenance receipt semantics. These details materially affect safe invocation.

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?

The description is front-loaded with the key action and avoids filler, but it is dense and packs multiple concepts into semicolon-heavy sentences. It remains efficient for a complex destructive tool, though slightly more structure would improve readability.

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 async whole-solution import with no output schema, the description covers the main safety, matching, replay, and receipt concerns. It does not explicitly explain how to poll import status via the available sibling, but it provides enough behavioral context to call the tool cautiously.

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?

The schema already documents many parameters, and the description adds useful meaning around candidate bytes, allow flags, and structured edits. However, it refers to a 'planHash' that is not named in the schema, and it does not clarify key relationships such as source versus candidate files or the change operation variants beyond high-level context.

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 first sentence clearly states the specific action: preview then submit a native async import into an existing unmanaged solution for reviewed classic Ribbon edits. It distinguishes this whole-solution import from narrower Ribbon editing and publication 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?

The description gives strong usage context: preview first, require exact candidate bytes and matching baseline, and execute with specific allow flags. It also lists exclusions such as no upgrade, managed, override, or automatic publish, but it does not explicitly name the sibling alternatives 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