Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_exception_info

Read-onlyIdempotent

Retrieve details about the current exception when the debugger is stopped on it, enabling diagnosis of .NET application failures.

Instructions

Get information about the current exception.

State: STOPPED required (stopped on exception).

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

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

Input Schema

NameRequiredDescriptionDefault
thread_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

B3.4/5.0
Behavior4/5

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

Description adds the state requirement beyond annotations (readOnlyHint, idempotentHint). Provides an escape hatch hint, adding behavioral context without contradiction.

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?

Extremely concise, three sentences each serving a purpose: purpose, state requirement, escape hatch hint. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks description of return value or how thread_id affects results. With no output schema, the agent cannot anticipate what information is returned, reducing completeness for a simple tool.

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

Parameters2/5

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

With 0% schema coverage, the description must clarify the thread_id parameter, but it does not. No additional meaning is provided beyond the schema's type and default.

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?

Description states 'Get information about the current exception' with a specific verb and resource. It is clear what the tool does, but does not explicitly differentiate from siblings like get_exception_context.

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?

Specifies required state 'STOPPED required (stopped on exception)', providing clear context for when to use. However, no mention of when not to use or comparison with alternative tools.

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