Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_build_diagnostics

Read-onlyIdempotent

Retrieve full build diagnostics and hidden warnings to investigate why a .NET app compiles but crashes or behaves unexpectedly. Reveals nullable, deprecation, and platform warnings.

Instructions

Get full build diagnostics including all warnings.

Build warnings are hidden by default in start_debug/restart_debug responses to reduce context noise. Call this tool when:

  • Build succeeds but the app crashes or behaves unexpectedly

  • Investigating assembly loading or compatibility issues

  • Checking nullable reference, deprecation, or platform warnings

  • Debugging "it compiles but doesn't work" situations

After a restore or build process completes with a failure, the result includes its stage (command), actual argv (commandLine), workingDirectory, exit code, and captured stdout/stderr even when no MSBuild diagnostics were parsed. Partial process output from timeout or cancellation is not retained. include_warnings filters structured diagnostics only; captured failure output is preserved unchanged. Command metadata is omitted when no process command was executed.

Args: include_warnings: Include warning details (default True, the point of this tool)

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

Input Schema

NameRequiredDescriptionDefault
include_warningsNo

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 cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), yet the description adds substantial beyond-annotation context: partial process output from timeout/cancellation is NOT retained, include_warnings filters structured diagnostics only while captured failure output is preserved, and command metadata is omitted with no executed process. These are real behavioral caveats. Minor ding because the return-field narrative strays beyond what an agent choosing the tool needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, followed by the usage bullets and then args, in a logical order. It is somewhat long and the failure-output paragraph is dense, but nearly every sentence carries distinct information rather than restating the schema.

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?

With no output schema and zero parameter descriptions, the description carries the full load and delivers: it enumerates the failure-result fields (stage/command, commandLine, workingDirectory, exit code, stdout/stderr) and explicitly notes what is omitted (metadata when no process ran, partial output on timeout/cancellation). An agent knows both when to call it and what to expect back.

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% (the single 'include_warnings' property has no description), so the description must compensate and largely does: it states the default (True), frames it as 'the point of this tool', and clarifies that the flag filters structured diagnostics only while never touching captured failure output. That is meaningful semantics beyond the bare boolean in the schema.

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?

States a specific verb and resource ('Get full build diagnostics including all warnings') and immediately distinguishes itself from siblings by noting that warnings are hidden by default in start_debug/restart_debug responses. An agent can tell what it retrieves and why it exists as a separate tool without opening the schema.

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?

Explicit 'Call this tool when:' list gives four concrete triggering scenarios (app crashes despite successful build, assembly loading issues, nullable/deprecation/platform warnings, 'compiles but doesn't work'). It also names the conditions under which the sibling tools suppress this data, so the routing decision is unambiguous.

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