Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

configure_exceptions

Idempotent

Configure exception filters to control when the debugger pauses on exceptions. Specify 'all' or 'user-unhandled', or pass an empty list to stop pausing.

Instructions

Configure which exceptions should pause the debugger.

Controls exception breakpoints — when the debugger should stop on exceptions. By default, no exception filters are set (exceptions don't pause unless uncaught).

Common filters supported by netcoredbg:

  • "all": Break on all exceptions (caught and uncaught)

  • "user-unhandled": Break on exceptions not handled in user code

Pass an empty list to disable all exception breakpoints.

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

Args: filters: List of exception filter names. Pass [] to disable.

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": "configure_exceptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already provide idempotent and open world hints. Description adds context about default behavior and effect of empty list. Does not contradict annotations and provides useful additional behavioral info.

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?

Starts with a one-line summary, followed by detailed explanation, examples, and escape hatch note. Every sentence adds value, no fluff.

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?

For a simple single-parameter tool with good annotations, the description covers purpose, usage, parameter, and defaults. No gaps.

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

Parameters5/5

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

The only parameter 'filters' is thoroughly described with examples ('all', 'user-unhandled') and instruction to pass [] to disable. Schema coverage is 0%, so description fully compensates.

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 states the tool configures exception breakpoints for the debugger. The verb 'configure' and resource 'exceptions' are distinct from sibling breakpoint tools that add specific breakpoints. Differentiates well.

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?

Explains default behavior (no filters set) and how to disable (empty list). Lists common filters. Could be more explicit about when to use this vs add_breakpoint, but the purpose is clear.

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

Deploy Server

Other Tools