windows-debug-mcp

Overview Schema Source Related Servers Discussions Admin

get_gpu_info

Retrieve graphics adapter details, driver version and date, VRAM, and display mode to diagnose VIDEO_TDR_FAILURE or game crashes.

Instructions

Graphics adapters, driver versions and dates, VRAM and the current display mode.

The driver version and date are the first thing to check against a VIDEO_TDR_FAILURE or a game that crashes on launch.

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

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

Behavior3/5

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

No annotations are provided, so the description carries full burden. It implies a read-only snapshot of GPU info but doesn't explicitly state non-destructiveness or potential performance impact. Still, the behavior is straightforward for a getter.

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 concise sentences: the first specifies what is returned, the second adds a practical usage hint. No wasted words, information is front-loaded.

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?

Given zero parameters and an output schema, the description adequately covers the tool's purpose and a key use case. Could mention it's a snapshot, but overall complete for a simple data retrieval 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?

No parameters exist, so per rules the baseline is 4. Schema coverage is 100% (trivially), and the description adds no extra parameter meaning but is not required.

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 the tool retrieves graphics adapter details, driver versions/dates, VRAM, and display mode. This distinguishes it from siblings like get_display_info or get_system_overview, which cover different hardware aspects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a specific use case: checking driver version for VIDEO_TDR_FAILURE or game crashes. While it doesn't explicitly exclude other contexts or mention alternatives, the hint is actionable and relevant.

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