windows-debug-mcp

by emyk

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_memory_modules

Retrieves installed RAM module details (size, speeds, part numbers) to identify mismatches causing bug checks.

Instructions

Installed RAM modules: size, rated speed, configured speed and part numbers.

Modules running below their rated speed mean XMP/EXPO is off; mixed speeds or a configured speed above the rating point at an overclock, which is the usual suspect behind MEMORY_MANAGEMENT and WHEA bug checks.

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

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?

No annotations are provided, so the description carries the full burden. It discloses the tool returns module attributes and provides diagnostic context (e.g., XMP/EXPO, WHEA errors), which is valuable. However, it does not explicitly state that it is read-only, though that is implied.

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 with zero wasted words. Each sentence adds meaningful information: what is returned and how to interpret it.

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 the tool has no parameters and an output schema exists, the description fully explains the return values (size, speeds, part numbers) and adds diagnostic interpretation, making it complete for a read-only hardware information tool.

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?

There are no parameters, so the baseline is 4. The description does not need to add parameter information; it correctly focuses on results.

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 retrieves installed RAM modules with specific attributes (size, rated speed, configured speed, part numbers). It is distinguishable from sibling tools like get_gpu_info 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?

No explicit guidance on when to use this tool over alternatives. The description implies it is for RAM-related diagnostics (e.g., checking speed mismatches), but does not say when not to use it or name alternative tools.

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