windows-debug-mcp

by emyk

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_boot_performance

Retrieves boot and shutdown timings, identifying which applications, services, or drivers caused delays.

Instructions

Boot and shutdown timings, plus what specifically slowed them down.

Windows measures every boot and records which applications, services and drivers took longer than expected. Slow boots almost always have a named culprit here.

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

Input Schema

Name	Required	Description	Default
`max_events`	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.8/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool retrieves historical boot timing data and points to specific culprits, which is transparent for a read-only diagnostic tool. However, it could mention system load or permission requirements.

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 three sentences with clear front-loading: the first sentence states the main output, the second provides context, and the third gives practical insight. No redundant information.

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's simplicity (one optional parameter, output schema exists), the description covers the core functionality but lacks guidance on the parameter. It is adequate but not fully complete; the parameter should be explained.

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 description coverage is 0%, meaning the parameter 'max_events' lacks a schema description. The tool description does not mention the parameter or its effect (limiting results), failing to compensate for the missing schema documentation.

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 it provides boot and shutdown timings and identifies what slowed them down. This is specific and distinguishes it from siblings, none of which cover boot performance.

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 for diagnosing slow boots ('Slow boots almost always have a named culprit here') but does not explicitly state when to use vs. alternatives or provide exclusions. Usage is implied, not explicit.

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