Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

export_solution

Exports an unmanaged or managed Dynamics 365 solution to a new local ZIP file; preview first, then execute with a plan hash to write validated output without overwriting.

Instructions

Preview by default. Native ExportSolution from a visible ordinary unmanaged source; choose managed output explicitly. Current CSDL and caller/environment identity are validated. Execute with planHash; writes an exclusive new local .zip, verifies identity/hash, never returns base64 or overwrites files. No publish. On failure the reserved path can be empty/partial; no automatic replay.

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true. Execution requires a current preview planHash.
dry_runNoDefault true. Execution requires a current preview planHash.
managedNo
outputPathNoAbsolute local file path. ZIPs are read without extraction or execution.
output_pathNoAbsolute local file path. ZIPs are read without extraction or execution.
expectedHashNo
expected_hashNo
solutionUniqueNameNo
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
solution_unique_nameNo

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

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

Beyond the annotations it discloses substantial behavior: it writes an exclusive new local .zip, never overwrites files, never returns base64, verifies identity and hash, does not publish, and on failure the reserved path may be empty or partial with no automatic replay. Those details about write semantics and failure modes are exactly what the annotations do not convey.

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 critical fact (preview by default) is front-loaded and nearly every clause carries information. The telegraphic, semicolon-heavy phrasing and compressed fragments like 'Native ExportSolution from a visible ordinary unmanaged source' cost some 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 parameter-heavy mutation tool with no output schema, the description covers defaults, execution gating, file behavior, verification, and failure handling. The main gap is that it does not say where a planHash comes from or what a preview returns, which an agent needs to complete the flow.

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 50% schema coverage the description carries real weight: it clarifies the dry_run default, explains that managed must be set explicitly, ties output_path to exclusive .zip creation, and references hash/identity verification and the environment identity check. It does not explain how expected_hash or environment_profile are used in any detail, and it references a 'planHash' that does not appear as an input property, leaving some ambiguity.

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?

The description names a specific verb and resource ('Native ExportSolution') and states the preview-by-default scope plus the managed/unmanaged choice, so an agent knows this produces a solution package. It does not name siblings such as import_solution_async or backup_customization to sharpen the boundary, so it falls short of a 5.

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 lays out a clear two-phase workflow: preview by default, then execute with a current planHash, and explicitly says managed output must be requested rather than assumed. What is missing is routing guidance against alternatives (e.g. when to use import/inspect or backup tools 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