Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_solution_import_status

Read-only

Retrieves Dynamics 365 solution import status from a supplied async operation or import job ID in one read, returning progress, terminal state, and solution identity evidence without polling.

Instructions

Read native asyncoperation and/or importjob by explicit receipt IDs once, without polling or resubmission. Separates terminal async state, progress, unavailable/hidden/forbidden evidence and solution identity readback. Caller-supplied IDs are independent observations, not an independently verified relation. Progress=100/identity match is not deployment/runtime proof. No raw job/log/configuration text returned.

Input Schema

NameRequiredDescriptionDefault
importJobIdNo
import_job_idNo
asyncOperationIdNo
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?

Beyond the readOnlyHint annotation, the description discloses the shape of the evidence returned: separated terminal async state, progress, unavailable/hidden/forbidden evidence, and solution identity readback. It also actively guards against misinterpretation ('Progress=100/identity match is not deployment/runtime proof') and states that no raw job/log/configuration text is returned, which sets expectations about response content and permissions-driven visibility.

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 short, front-loaded with the action and scope, and every sentence carries content — scope, output categorization, caveats. It is dense with technical qualifiers, but nothing is redundant padding; a slightly more explicit opening linking it to the import workflow 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?

There is no output schema, and the description compensates by enumerating what categories of evidence come back and warning about how to interpret terminal state and solution identity. For a read-only lookup tool with a permissive anyOf schema this is nearly complete; the only gap is the unstated behavior when both an async operation ID and an import job ID are supplied simultaneously.

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 only 20%, so the description must carry more weight than usual. It does add meaning with 'asyncoperation and/or importjob by explicit receipt IDs', clarifying that either or both ID families may be supplied and that IDs are caller-supplied observations rather than verified relations. It does not explain the alias variants (async_operation_id vs asyncOperationId) or the at-least-one-required anyOf constraint beyond the loose 'and/or' phrasing.

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 states a specific verb and resource: it reads native asyncoperation and/or importjob records by explicit receipt IDs. It distinguishes the scope ('once, without polling or resubmission') and hints at the boundary with log-reading siblings ('No raw job/log/configuration text returned'), but it never names an alternative tool, so the differentiation is implicit rather than explicit.

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 phrase 'once, without polling or resubmission' implies the intended call pattern (a single status check after an import, not a loop), which is useful implied guidance. However, there is no explicit statement of when to choose this over get_solution_import_log or verify_solution_deployment, and no stated prerequisites or exclusions. Usage is inferable but not spelled out.

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