Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_solution_snapshot

Read-only

Capture a Dynamics 365 solution snapshot, including environment settings and caller-visible membership, as JSON for comparing separately configured environments.

Instructions

Capture the configured environment and current-caller explicit visible membership with selected properties. Profiles: 1 table, 9 global Picklist, 10 relationship, 61 Web Resource, 91 non-package database assembly. Binary content is hashed, never returned/executed. Normalize labels/option values and retain IDs only as evidence. Unsupported/forbidden/partial/unstable inventory is explicit. No nested expansion, atomic snapshot, publication, full schema/dependency/runtime proof. Pass or save the returned snapshot JSON to compare separately configured environments.

Input Schema

NameRequiredDescriptionDefault
topNoMaximum memberships, default 100. A truncated inventory is inconclusive.
maxPagesNoMaximum native pages, default 5.
max_pagesNoMaximum native pages, default 5.
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

B3.2/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses genuine behavioral traits: binary content is hashed and never returned or executed, labels/option values are normalized while IDs are retained only as evidence, and unsupported/forbidden/partial/unstable inventory is explicitly surfaced rather than silently dropped. The explicit non-goals (no nested expansion, not atomic, no publication, no full schema/dependency/runtime proof) tell the agent exactly what the output cannot prove. With annotations covering safety, this is a strong addition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the limitations block is well placed, but the telegraphic sentence fragments ("Profiles: 1 table, 9 global Picklist, 10 relationship...") are hard to parse and the component-type code list occupies a large share of the text without being tied to any parameter.

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

Completeness3/5

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

For a complex, six-parameter, no-output-schema tool, the description covers behavior and limits well but leaves two real gaps: the alias semantics of the solution identifier and any indication of the snapshot JSON's shape. It is adequate to call the tool correctly, but not complete on the identifier/return-structure front.

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 67%, so the schema already documents top, max_pages/maxPages, and environment_profile. The description adds "selected properties" but nowhere explains top vs max_pages, and critically never addresses the solution_unique_name / solutionUniqueName alias pair that the allOf-anyOf schema makes ambiguous. The profile-to-component-type mapping is useful context but does not map to any parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Capture the configured environment and current-caller explicit visible membership with selected properties" conveys an inventory/snapshot read, but the word "solution" never appears in the description body — it only surfaces through the component-type profile list and the tool name. Nothing distinguishes it from siblings such as inspect_solution_package, list_solution_components, or export_solution, so the agent must infer which inventory tool this is.

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 final sentence implies the workflow: persist the returned JSON and compare separately configured environments, which hints at drift detection. However, it never names compare_solution_snapshots, verify_solution_deployment, or export_solution as the alternative paths, and gives no when-not-to-use guidance (e.g., use export_solution when you need an installable package).

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