Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ui_send_keys

Sends keyboard input to a UI element in .NET applications. Supports modifier keys, special keys, and fallback to element search for reliable automation.

Instructions

Send keyboard input to a UI element.

Note: If app is STOPPED at breakpoint, resume with continue_execution() first.

Tries cached coordinates first (click to focus, then send keys), then falls back to pywinauto element search.

Key syntax (modifiers are PREFIX characters, special keys in braces):

  • Regular text: "hello world"

  • Modifiers: ^ = Ctrl, % = Alt, + = Shift

  • Alt+Z: "%z" Alt+F4: "%{F4}"

  • Ctrl+C: "^c" Ctrl+Shift+S: "^+s"

  • Shift+Tab: "+{TAB}"

  • Special keys: {ENTER} {TAB} {ESC} {DELETE} {BACKSPACE}

  • Arrow keys: {LEFT} {RIGHT} {UP} {DOWN}

  • Navigation: {HOME} {END} {PGUP} {PGDN}

  • Function keys: {F1} {F2} ... {F12}

  • Physical keypad: {NUMPAD0} ... {NUMPAD9}, {NUMPADADD}, {NUMPADSUBTRACT}, {NUMPADMULTIPLY}, {NUMPADDIVIDE}, {NUMPADDECIMAL}, {NUMPADENTER}, {NUMLOCK} (press/release, not lock-state setting)

  • Combined: Ctrl+End = "^{END}", Alt+Z = "%z"

IMPORTANT: Modifier prefixes (^%+) apply to the NEXT character or {KEY}. For Alt+Z send "%z" (NOT "{ALT}z" or "Alt+Z").

Args: keys: Keys to send (see syntax above) automation_id: Target element's AutomationId name: Target element's Name control_type: Target element's control type

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": {
      "keys": "<keys>"
    },
    "name": "ui_send_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYes
nameNo
xpathNo
root_idNo
control_typeNo
automation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

A3.9/5.0
Behavior4/5

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

With only openWorldHint=false in annotations, the description adds substantial behavioral detail: it tries cached coordinates first (clicking to focus then sending keys) and falls back to pywinauto element search. It also notes the breakpoint resume requirement and provides extensive key syntax. It does not, however, describe side effects (e.g., whether typed text modifies application state) or return behavior.

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 front-loaded with purpose and a key prerequisite, then organized into clear sections using bullets and examples. The key syntax section is necessarily detailed, but every sentence earns its place by explaining a distinct aspect of the tool's operation or syntax.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, no output schema, minimal annotations), the description covers essential aspects: purpose, prerequisite, fallback behavior, and comprehensive key syntax. It omits some parameter details (xpath, root_id) and return-value information, but provides enough for an agent to invoke the tool correctly in most common scenarios.

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?

Schema description coverage is 0%, so the description must compensate. It thoroughly documents the required 'keys' parameter with syntax rules, and briefly names automation_id, name, and control_type. However, it omits xpath and root_id entirely and does not explain how the target-identification parameters interact or take precedence, leaving significant gaps for 6 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Send') and resource ('keyboard input to a UI element'), making the tool's purpose clear. However, it does not differentiate itself from siblings like ui_send_keys_focused or ui_key_sequence, leaving the agent to infer when this tool is preferable.

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

Usage Guidelines4/5

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

The description provides a clear prerequisite: 'If app is STOPPED at breakpoint, resume with continue_execution() first.' It also describes the internal approach (cached coordinates then fallback), which helps the agent understand operational context. However, it does not explicitly compare with alternative sibling tools or state when not to use it.

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