Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_solution_import_log

Read-only

Read a solution import job's native XML by GUID and return bounded summaries that prioritize failures and warnings, with optional redacted error text and no raw XML.

Instructions

Explicitly read a native solution importjob data XML by GUID and return bounded result summaries. <=2 MiB XML; no DTD/entities/namespaces or execution. Counts include manifest/section results, not unique components; failures/warnings prioritized. Raw XML is never returned. Error text is opt-in and bounded with best-effort credential redaction. Logs do not prove async completion or deployment; missing/forbidden/unsupported data is distinct from success. Uses importjobs, not record-data importlogs.

Input Schema

NameRequiredDescriptionDefault
topNoReturned result limit, default 50. Complete bounded XML counts are retained.
importJobIdNo
includeTextNoDefault false. True can expose sensitive business text even after best-effort credential redaction.
include_textNoDefault false. True can expose sensitive business text even after best-effort credential redaction.
maxTextCharsNoPer message limit, default 2048.
import_job_idNo
max_text_charsNoPer message limit, default 2048.
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

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses substantial behavior: XML size limits, no DTD/entities/namespaces or execution, manifest/section count semantics, failure/warning prioritization, no raw XML return, opt-in bounded error text, best-effort credential redaction, and the distinction between missing/forbidden/unsupported data and success.

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 core purpose and scope are front-loaded, and the dense clauses mostly carry useful constraints. The semicolon-heavy single paragraph is slightly harder to scan than a more structured presentation, but it avoids filler.

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 import log tool with no output schema, the description covers return behavior, security constraints, caveats about completion proof, and error/data-state distinctions. It stops short of describing the exact summary fields, but provides enough context for correct invocation.

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?

The schema already documents most parameters, and the description adds useful meaning by specifying that the job is identified by GUID, summaries are bounded, and text exposure is opt-in with redaction. It does not clarify every parameter such as environment_profile or the alias pairs, but it compensates well for the key semantics.

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?

The description states a specific verb and resource: read a native solution importjob data XML by GUID and return bounded summaries. It also clearly scopes the resource with 'Uses importjobs, not record-data importlogs,' distinguishing it from record-data log tools.

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 clear context for reading import job logs and explicitly excludes record-data importlogs. However, it does not explicitly route the agent to sibling tools such as get_solution_import_status or verify_solution_deployment when async status or deployment verification is needed.

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