Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

import_solution_async

Destructive

Previews or executes the first import of an ordinary unmanaged ZIP into a configured Dynamics 365 environment; execution needs a current planHash and acceptance of shared unmanaged component changes.

Instructions

Preview first import of an ordinary unmanaged ZIP into the configured environment. Execute with planHash and allow_unprotected_write=true. Same solution-name updates, managed/patch/upgrade imports are blocked. First import can change shared unmanaged components. Fixed overwrite overlay/workflow activation/dependency skip/holding/upgrade flags false; no environment overrides or separate publish. Submits once using ImportSolutionAsync; accepted is not completed. Unknown outcomes retain a client-assigned importJobId for manual status checks.

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true. Execution requires a current preview planHash.
dry_runNoDefault true. Execution requires a current preview planHash.
filePathNoAbsolute local file path. ZIPs are read without extraction or execution.
file_pathNoAbsolute local file path. ZIPs are read without extraction or execution.
expectedHashNo
contentBase64NoCanonical base64; ZIP bytes at most 32 MiB. Supply exactly one input source.
expected_hashNo
content_base64NoCanonical base64; ZIP bytes at most 32 MiB. Supply exactly one input source.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
allowUnprotectedWriteNoExplicitly accept the native import concurrency window and shared unmanaged component changes.
allow_unprotected_writeNoExplicitly accept the native import concurrency window and shared unmanaged component changes.

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.1/5.0
Behavior4/5

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

Beyond annotations declaring destructive=true and idempotent=false, it discloses that the operation submits once asynchronously, that acceptance is not completion, that a first import can mutate shared unmanaged components, and that unknown outcomes leave an importJobId for later checks. It does not cover rollback behavior or permission requirements.

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 and has no filler; each sentence addresses a distinct behavior such as preview, execution constraints, blocked import types, side effects, and async semantics. It is dense and telegraphic with semicolon-packed clauses, which slightly reduces 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, destructive async import with no output schema, it covers the preview/execute model, blocked cases, side effects, acceptance semantics, and job-ID tracking. The missing detail is how the preview yields or maps to planHash and how status polling should be performed, though the latter is hinted at.

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 description coverage is 82%, so the schema already carries most parameter meaning; the description adds context about dry-run preview, allow_unprotected_write, and fixed internal flags. However, it refers to a 'planHash' execution value that has no matching schema property and does not explain the expectedHash field, creating avoidable ambiguity.

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?

Opens with a precise verb and resource: 'Preview first import of an ordinary unmanaged ZIP into the configured environment.' It immediately distinguishes this operation from same solution-name updates and managed/patch/upgrade imports, so an agent can identify it without opening the 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?

It gives a clear two-step flow: preview first, then execute with planHash and allow_unprotected_write=true. It also states what is blocked, including same solution-name updates and managed/patch/upgrade imports. It stops short of naming sibling alternatives such as get_solution_import_status, and the referenced planHash is not present as a named schema parameter.

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