Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

diagnose_plugin_failure

Read-only

Builds a read-only evidence report from exception-filtered traces, failed jobs, and current plugin steps to investigate Dynamics 365 plugin failures by correlation ID, step, or plugin type.

Instructions

Build a read-only evidence report from exception-filtered traces, failed jobs and current plugin steps, anchored by correlation, step or plugin type. Uses native IDs for links, reports missing/forbidden/limited sources and keeps root cause undetermined. Current step state is not historical configuration.

Input Schema

NameRequiredDescriptionDefault
topNoMaximum visible rows, default 50. Reaching this bound is not a complete inventory.
stepIdNoCompatibility alias for step_id; conflicting values are rejected.
toTimeNoCompatibility alias for to_time; conflicting values are rejected.
step_idNo
to_timeNoISO timestamp with explicit timezone, inclusive. Default current UTC time.
fromTimeNoCompatibility alias for from_time; conflicting values are rejected.
maxPagesNoCompatibility alias for max_pages; conflicting values are rejected.
from_timeNoISO timestamp with explicit timezone, inclusive. Default 24 hours before to_time.
max_pagesNoMaximum native pages, default 5. Bounded reads report incompleteness.
includeTextNoCompatibility alias for include_text; conflicting values are rejected.
include_textNoDefault false. Opt in to trace/exception/job message text, which can contain business data. Secure/unsecure configuration columns are never selected.
maxTextCharsNoCompatibility alias for max_text_chars; conflicting values are rejected.
correlationIdNoCompatibility alias for correlation_id; conflicting values are rejected.
correlation_idNo
max_text_charsNoPer-text preview limit, default 2000; truncation is explicit.
pluginTypeNameNoCompatibility alias for plugin_type_name; conflicting values are rejected.
plugin_type_nameNo
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.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description adds real behavioral context: it reports missing/forbidden/limited sources and deliberately keeps root cause undetermined. The caveat that 'current step state is not historical configuration' prevents a common misreading of the output, which is beyond what annotations convey, though pagination/truncation behavior is only covered in the schema.

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?

Three dense sentences with the artifact and scoping front-loaded and no filler. The final sentence is slightly cryptic in isolation but carries a legitimate warning.

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 an 18-parameter report builder with no output schema, the description conveys the report's composition, link identity scheme, and completeness caveats, which is close to sufficient. It stops short of describing the report's shape or what 'undetermined root cause' means for next steps.

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 83% schema description coverage the baseline is 3; the description earns an extra point by explaining the anchoring semantics (correlation, step, or plugin type) that drive the schema's anyOf requirement and by noting native IDs are used for links. It does not document the alias/conflict-resolution behavior, but the schema already does that.

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?

States a specific verb and artifact ('Build a read-only evidence report') over specific sources (exception-filtered traces, failed jobs, current plugin steps), which distinguishes it from single-source siblings like query_plugin_trace_logs or query_failed_system_jobs. It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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?

The name plus 'anchored by correlation, step or plugin type' gives clear context for when this applies and how to scope the call, matching the schema's anyOf. It does not state when NOT to use it or route the agent to the narrower query 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