Skip to main content
Glama

windbg_go

Resume a WinDbg session and wait for events without forcing break-in on timeout. Filter output, stop on exceptions, and detect quiet periods to gather debugging information.

Instructions

Recommended safe continue: send cdb 'g', then wait for event/output without ever sending break-in on timeout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeoutNoAbsolute seconds to wait; timeout does not pause the target
max_linesNoMaximum raw event lines to read
tail_linesNoReturn only the last N filtered event lines
ignore_caseNoApply include/exclude regexes case-insensitively
invert_matchNoWith filter_pattern, keep non-matching lines instead of matching lines
context_afterNoInclude this many lines after each filter_pattern match
quiet_timeoutNoReturn after this many quiet seconds once output has arrived, unless stop_on_exception=true and no exception was seen
context_beforeNoInclude this many lines before each filter_pattern match
filter_patternNoOptional regex; when set, only matching event lines are returned
exclude_patternNoOptional regex; matching event lines are removed before include filtering
stop_on_exceptionNoWhen true, ignore quiet output gaps until exception-like event, prompt, process exit, or timeout
Behavior4/5

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

The description discloses a key behavioral trait: it never sends break-in on timeout, meaning the target may keep running after the tool returns. It also states it sends 'g' and waits for output. With no annotations provided, this disclosure carries the transparency burden. It does not cover side effects on target state or exact return behavior, but the critical safety guarantee is clearly stated.

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 a single sentence that front-loads the key phrase 'Recommended safe continue' and explains the command, wait behavior, and timeout policy with zero filler. It is appropriately concise.

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?

The description gives the core behavior but leaves out return format details, the relationship to other windbg wait/continue commands, and how the filtering parameters interact. The schema covers parameters well, but the tool's overall operational context (e.g., when it returns, what counts as output) is only partially specified. Adequate for a simple tool but with clear gaps for an 11-parameter command.

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

Parameters3/5

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

The input schema has 100% coverage of parameter descriptions, so the schema itself documents all 11 parameters. The description adds no parameter-specific semantics beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action: send 'g' to cdb and wait for event/output, framing it as a 'Recommended safe continue.' This distinguishes it from a plain continue by emphasizing the safe no-break-in behavior, though it does not explicitly name sibling tools. Overall, the purpose is clear but sibling differentiation is only implicit.

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 phrase 'Recommended safe continue' gives a recommendation, and the description explains the safe behavior (never sending break-in on timeout). However, it does not explicitly say when to use this versus windbg_continue, windbg_continue_async, or windbg_wait_for_event, nor does it state exclusions. Usage is implied but not fully explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DdUdle/ctxdebug'

If you have feedback or need assistance with the MCP directory API, please join our Discord server