Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ui_release_modifiers

Release keyboard modifiers held during .NET UI debugging, either specific ones or all at once, to restore normal input behavior.

Instructions

Release held modifiers or all held modifiers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "modifiers": "<modifiers>"
    },
    "name": "ui_release_modifiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
modifiersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

B3.4/5.0
Behavior2/5

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

The description lacks details about behavior beyond the core action. It does not explain what 'all held modifiers' means, potential side effects, or any restrictions, and the annotation only provides openWorldHint=false without additional context.

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?

The description is a single, short sentence that is front-loaded and immediately conveys the tool's purpose. No unnecessary words.

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?

Given the tool's simplicity, the description omits important context such as prerequisites (must have held modifiers), return behavior, and error conditions. It is incomplete for a tool with no output schema and minimal annotations.

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

Parameters3/5

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

The description adds some meaning by indicating the parameter can accept a list or a single string and mentions 'all held modifiers', but it does not explain valid values or how to specify 'all', leaving ambiguity.

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?

The description clearly states the action (release) and the resource (held modifiers), and it distinguishes itself from sibling tools like ui_hold_modifiers and ui_get_held_modifiers by focusing on release.

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?

The description does not explicitly state when to use this tool versus alternatives or provide prerequisites (e.g., modifiers must be held first). The usage context is implied but not clarified.

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