breakpoint-mcp-tools-guide

What problem does it solve?

This guide helps Copilot choose and call the extension's breakpoint and debug-session MCP tools correctly so users can inspect, modify, and control VS Code breakpoints and debug sessions without ambiguity or parameter errors.

Core Features & Use Cases

• Tool selection guidance: Recommends which MCP tool to call first (for example, list_breakpoints or list_debug_sessions) based on the user's intent.
• Parameter and resolution rules: Explains filePath vs workspaceFolderPath, functionName, 1-based line/column semantics, sessionId usage, and list-first discovery for ambiguous targets.
• Recommended workflows: Stepwise patterns for listing state, updating by key, using update_breakpoint vs add/remove, and controlling debug sessions (pause/continue/step/restart).
• Use case: When a user asks to add or remove breakpoints across a multi-root workspace, the guide ensures Copilot collects the correct workspaceFolderPath, resolves the target file path, and chooses the appropriate add_source_breakpoint or remove_breakpoint call.

Quick Start

Ask Copilot to list all breakpoints in the workspace and then specify the exact add, update, or remove action including filePath or key and a 1-based line number.