mcp-netcoredbg
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Each tool has a clearly distinct purpose within the .NET debugging domain, with no significant overlap. For example, 'step_into', 'step_over', and 'step_out' are distinct stepping operations, while 'launch' and 'launch_watch' cover different startup modes. The descriptions reinforce these distinctions, making misselection unlikely.
Tool names follow a highly consistent snake_case pattern with clear verb_noun or verb-only structures, such as 'set_breakpoint', 'list_sessions', and 'continue'. There are no deviations in naming conventions, making the set predictable and easy to navigate for an agent.
With 25 tools, the count is on the higher side for a debugging server, which might feel heavy but is reasonable given the comprehensive coverage of debugging operations. It includes all essential actions like stepping, breakpoint management, and session control, though it borders on being extensive.
The tool set provides complete coverage of the .NET debugging lifecycle, including session management (launch, attach, terminate), execution control (continue, pause, step operations), breakpoint handling, variable inspection, and status monitoring. There are no obvious gaps, ensuring agents can handle all typical debugging workflows without dead ends.