windows-debug-mcp

Overview Schema Source Related Servers Discussions Admin

list_error_reports

List the newest Windows Error Reporting reports to identify application crashes and hangs, including those without saved dump files.

Instructions

List Windows Error Reporting reports, newest first.

Every application crash and hang leaves one of these even when no dump file was kept, so they are often the only remaining record.

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": "list_error_reports"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses ordering (newest first) and the nature of reports (only remaining record sometimes). However, it does not mention that limit parameter controls count, or if pagination exists. Adequate but not thorough.

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?

Two sentences; first states purpose and ordering, second adds valuable context. No fluff, every sentence earns its place.

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?

Given the tool is simple and has an output schema, the description covers the core purpose but omits the limit parameter. It is adequate for basic use but could be more complete by mentioning the parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description does not mention the 'limit' parameter at all. The parameter name is somewhat self-explanatory, but the description fails to add context like 'Specify the maximum number of reports to return', which would help the agent.

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 clearly states 'List Windows Error Reporting reports, newest first.' This is a specific verb (List) and resource (Windows Error Reporting reports), and it distinguishes from siblings like list_crash_dumps which deal with dump files.

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 usage when needing to see crash/hang records, especially when no dump files exist, but it does not explicitly state when to use this tool over alternatives like list_crash_dumps or get_crash_history. No exclusions or when-not guidance are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.