mcp-netcoredbg
Server Quality Checklist
Latest release: v2.0.0
- Disambiguation5/5
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.
Naming Consistency5/5Tool 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.
Tool Count3/5With 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.
Completeness5/5The 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.
Average 3.2/5 across 25 of 25 tools scored. Lowest: 2.3/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add
glama.jsonto the root of your repository:{ "$schema": "https://glama.ai/mcp/schemas/server.json", "maintainers": [ "your-github-username" ] }Then . Browse examples.
Add related servers to improve discoverability.
How to sync the server with GitHub?
Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.
To manually sync the server, click the "Sync Server" button in the MCP server admin interface.
How is the quality score calculated?
The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).
Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.
Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).
Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.
GitHub Badge
Glama performs regular codebase and documentation scans to:
- Confirm that the MCP server is working as expected.
- Confirm that there are no obvious security issues.
- Evaluate tool definition quality.
Our badge communicates server capabilities, safety, and installation instructions.
Card Badge
Copy to your README.md:
Score Badge
Copy to your README.md:
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/AerialByte/mcp-netcoredbg'
If you have feedback or need assistance with the MCP directory API, please join our Discord server