Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ui_hold_modifiers

Keep keyboard modifier keys active across multiple UI automation inputs, so you can apply Ctrl, Shift, or Alt to subsequent interactions without re-sending them.

Instructions

Hold modifiers across subsequent UI input calls.

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

Input Schema

NameRequiredDescriptionDefault
modifiersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

B3/5.0
Behavior3/5

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

The description discloses that modifiers are held across subsequent calls, which is a key behavioral aspect. However, it does not address overlapping calls, state persistence, or edge cases. The sparse annotations (only openWorldHint) leave the description to carry the burden, which it partially does.

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?

The description is a single concise sentence with a clear verb and context. It could be slightly expanded with more detail without losing conciseness.

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 lack of parameter guidance, no output schema, and minimal annotations, the description is insufficient for an agent to use the tool correctly. It does not provide enough context about valid inputs or the tool's effect on other tools.

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

Parameters1/5

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

Schema coverage is 0% and the description does not explain what the 'modifiers' array should contain (e.g., valid strings like 'ctrl', 'shift'). The agent has no guidance on allowable values.

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 'Hold modifiers across subsequent UI input calls' clearly states the verb 'hold' and resource 'modifiers', and distinguishes from sibling tools like 'ui_release_modifiers' and 'ui_get_held_modifiers'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Missing when-not-to-use or tips about releasing modifiers after use.

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