windows-debug-mcp

by emyk

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_storage_health

Monitors disk SMART counters and free space to diagnose kernel data inpage errors, stutter, and failed updates.

Instructions

Disks, their SMART-derived health counters, and free space per volume.

Wear level, reallocated sectors and read errors here explain KERNEL_DATA_INPAGE_ERROR, stutter during loading screens and failed updates. A system volume below roughly 10% free also blocks crash dumps.

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_storage_health"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Discloses that the tool returns health counters and free space, and adds valuable context about low free space blocking crash dumps. With no annotations, this provides good behavioral insight for a read-only tool.

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 what is returned, second explains diagnostic relevance. No unnecessary words, and information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and an existing output schema, the description fully covers the tool's purpose and provides enough context for interpretation. It mentions key diagnostic use cases and constraints.

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?

No parameters exist, so the description does not need to add parameter meaning. The baseline of 4 applies, and the description effectively explains the tool's output without needing parameter details.

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?

Clearly states it retrieves disks, SMART health counters, and free space per volume. Provides specific examples of health counters and their relation to system issues, distinguishing it from sibling tools like get_pagefile_and_dump_settings or get_system_overview.

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?

Description implies usage for diagnosing storage-related issues (e.g., KERNEL_DATA_INPAGE_ERROR, stutter, failed updates) but does not explicitly state when to use this tool over alternatives or provide exclusions.

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