Skip to main content
Glama
thebtf

netcoredbg-mcp

by thebtf
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

start_debug

Start debugging a .NET program by launching it under the debugger with full call stack, variables, and breakpoints. Auto-resolves .exe to .dll for .NET 6+ apps to avoid errors.

Instructions

Start debugging a .NET program. RECOMMENDED for most debugging scenarios.

This is the preferred method for debugging .NET applications. It launches a new process under the debugger with full feature support including:

  • Complete call stack visibility

  • Full variable inspection

  • All breakpoint features

SMART RESOLUTION: For .NET 6+ apps (WPF/WinForms), automatically resolves .exe to .dll to avoid "deps.json conflict" errors. You can pass either App.exe or App.dll - the correct target will be selected automatically.

PRE-BUILD: By default, builds the project before launching to ensure you're debugging the latest code. Provide build_project path to .csproj file. Set pre_build=False to skip building (e.g., for pre-built binaries).

BUILD WARNINGS: Hidden by default to reduce noise. If the build succeeds but the app behaves unexpectedly, call get_build_diagnostics() to see all warnings — they may reveal the issue.

Use attach_debug only for already-running processes (e.g., ASP.NET services).

Escape hatch: see the dap-escape-hatch prompt for unwrapped DAP requests.

Args: program: Path to the .NET executable or DLL to debug (auto-resolved) cwd: Working directory for the program args: Command line arguments env: Environment variables launch_profile: Optional project launch profile name stop_at_entry: Stop at entry point pre_build: Build project before launching (default: True). Requires build_project. build_project: Path to .csproj file (required when pre_build=True) build_configuration: Build configuration (Debug/Release) stealth_mode: Avoid foreground-stealing UI actions for GUI debugging

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
programYes
cwdNo
argsNo
envNo
launch_profileNo
stop_at_entryNo
pre_buildNo
build_projectNo
build_configurationNoDebug
stealth_modeNo

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Discloses key behaviors: launches new process under debugger with full features, automatic .dll resolution for .NET 6+, default pre-build, hidden build warnings with option to retrieve via get_build_diagnostics, and stealth mode. Does not contradict annotations (openWorldHint=false). Could mention that launching a process is not read-only, but overall transparent.

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?

Well-structured with named sections (SMART RESOLUTION, PRE-BUILD, BUILD WARNINGS). Each sentence adds value. Concise yet informative, front-loaded with main purpose and key features.

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?

Covers smart resolution, pre-build, build warnings, stealth mode, and alternatives. Given 10 parameters and no output schema, description provides sufficient context for agent to use tool correctly. Could mention error handling or session management, but references sibling tools for diagnostics and stopping.

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?

Schema coverage is 0%, but description explains all parameters in the Args section, including auto-resolution for 'program', defaults and conditions for 'pre_build' and 'build_project', and purpose of 'stealth_mode'. Adds meaning beyond parameter names, though not all parameters have detailed constraints.

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 identifies the tool as starting debugging for .NET programs. Uses specific verb 'Start debugging' and resource '.NET program'. Distinguishes from sibling 'attach_debug' by stating it's for launching new processes, not attaching to running ones. Includes recommendations like 'RECOMMENDED' and 'preferred method'.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('most debugging scenarios'), when to use alternatives ('Use attach_debug only for already-running processes'), and provides conditional guidance (pre_build, build_project required). Also mentions escape hatch for DAP requests.

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/thebtf/netcoredbg-mcp'

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