Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

verify_solution_deployment

Read-only

Compares a configured Dynamics 365 target to an expected solution snapshot and reports scoped differences plus optional native job/import-log evidence, without modifying or repairing anything.

Instructions

Read-only selected-scope verification of the configured target against an expected snapshot. Returns a live snapshot comparison and, for explicit receipt IDs, independent native job/import-log evidence with text withheld. No full deployment/publication/runtime/causal package-job linkage is asserted, and job success never overwrites known component differences. Does not import, publish, repair, poll or replay.

Input Schema

NameRequiredDescriptionDefault
topNoMaximum memberships, default 100. A truncated inventory is inconclusive.
maxPagesNoMaximum native pages, default 5.
max_pagesNoMaximum native pages, default 5.
importJobIdNo
import_job_idNo
expectedManagedNo
asyncOperationIdNo
expectedSnapshotNoThe complete snapshot object from get_solution_snapshot, not the success wrapper. Versioned strict shape, <=2 MiB/200 memberships, canonical definitions and all hashes are checked. Hashes do not prove authenticity.
expected_managedNo
expected_snapshotNoThe complete snapshot object from get_solution_snapshot, not the success wrapper. Versioned strict shape, <=2 MiB/200 memberships, canonical definitions and all hashes are checked. Hashes do not prove authenticity.
async_operation_idNo
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
Behavior5/5

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

With only readOnlyHint=true in annotations, the description carries the behavioral burden and does so richly: it discloses what is returned (live snapshot comparison plus independent native job/import-log evidence with text withheld), what is explicitly not asserted (no deployment/publication/runtime/causal linkage), and a non-obvious rule that job success never overwrites known component differences. That last point is exactly the kind of interpretive caveat an agent could not get from 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?

Dense but front-loaded: the read-only verification framing comes first, then return semantics, then the caveats and exclusions. The sentences are long and clause-heavy, but each one adds a distinct constraint rather than repeating the schema.

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 read-only tool with 12 (alias-heavy) parameters, a strict nested snapshot object, and no output schema, the description covers return shape, evidence behavior and the limits of what the result proves. Remaining gaps are the pagination/truncation behavior and the meaning of expectedManaged, which the schema only partly documents.

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 50% and the description adds real meaning for the evidence path, explaining that receipt IDs (importJobId/asyncOperationId) trigger independent native job/import-log evidence with text withheld, and that the expected snapshot is compared against the live target. It says nothing about top/maxPages truncation semantics, expectedManaged, or environment_profile, leaving half the surface to the schema aliases.

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?

Names a specific verb and resource ('verification of the configured target against an expected snapshot') and bounds scope as 'selected-scope' and 'read-only'. It implicitly separates itself from siblings like get_solution_snapshot and compare_solution_snapshots by asserting a verification verdict rather than a raw comparison, but it never names those siblings or defines what 'configured target' means.

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 negative guidance ('Does not import, publish, repair, poll or replay') usefully rules out adjacent operations, and 'for explicit receipt IDs' hints that job/import-log evidence is optional. However there is no positive statement of when an agent should pick this over compare_solution_snapshots or get_solution_import_status, so the routing decision is left to inference.

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