Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

query_failed_system_jobs

Read-only

Read failed system jobs (statuscode 31) within completion-time bounds, optionally filtered by correlation or owning step ID, to diagnose failures without retrying or changing jobs.

Instructions

Read native failed system jobs (statuscode 31) using completion-time bounds and optional correlation/owning step IDs. Excludes job data/configuration and message text by default. Does not retry, cancel or change jobs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "query_failed_system_jobs"
  }
}

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.
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.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it excludes job data/configuration and message text by default, and explicitly states it does not retry, cancel, or change jobs.

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

Conciseness5/5

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

The description is compact and front-loaded: it states the read operation first, then the default exclusions, then the non-mutating guarantee. Every sentence carries useful information without repetition.

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 16-parameter query tool with no output schema, the description covers purpose, scope, key defaults, and safety behavior. It does not describe the return shape or pagination incompleteness, but those are partly handled by the schema and annotations.

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?

Schema description coverage is high at 88%, so the schema documents most parameters. The description still adds meaning by summarizing completion-time bounds, optional correlation/owning step IDs, and the default exclusion of message text, which helps an agent understand key filtering and privacy defaults beyond raw field descriptions.

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 uses a specific verb-resource pair: 'Read native failed system jobs (statuscode 31)'. It also scopes the read to completion-time bounds and optional correlation/owning step IDs, which clearly distinguishes it from generic job or trace-log queries.

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 description implies when to use the tool by naming failed system jobs and completion-time bounds, but it does not explicitly compare it with siblings such as query_plugin_trace_logs or diagnose_plugin_failure. It also lacks explicit when-not-to-use guidance.

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