Skip to main content
Glama
Sign In
agy_computer_use.mcp_server

agy_computer_use.mcp_server

by orakulzero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cu_bg_dispatch

Dispatch focusless mouse and keyboard actions—clicks, typing, scrolling, dragging—to a target window using PostMessageW or WM_SETTEXT for background automation.

Instructions

Dispatch focusless mouse/keyboard actions via PostMessageW or SendMessageTimeoutW(WM_SETTEXT).

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": {
      "hwnd": "<hwnd>",
      "action_type": "<action_type>"
    },
    "name": "cu_bg_dispatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
hwndYesTarget window handle (HWND).
textNoText to type or set.
norm_xNoX on [0..1000] grid.
norm_yNoY on [0..1000] grid.
dry_runNoSynthesize messages without OS dispatch.
drag_stepsNoIntermediate interpolation steps for drag.
end_norm_xNoEnd X on [0..1000] grid for drag.
end_norm_yNoEnd Y on [0..1000] grid for drag.
action_typeYesAction type (click, double_click, right_click, move, drag, scroll, type_text, wm_settext).
wheel_deltaNoScroll wheel delta (default -120).
desktop_nameNoDesktop session name (default 'Default').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It adds useful mechanism details (PostMessageW, SendMessageTimeoutW, WM_SETTEXT, focusless dispatch), but it omits side effects, permission or integrity-level requirements, failure modes, and whether messages may be ignored by target applications.

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 definition is a single front-loaded sentence with no filler. It is efficient, though quite sparse for an 11-parameter tool with no annotations or output schema.

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?

For a complex, multi-action background input dispatcher with no annotations and no output schema, the description is too thin. The schema covers parameters, but the description does not explain return behavior, reliability, failure handling, or routing among closely related sibling tools.

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 100%, so all 11 parameters are already documented in the schema. The description adds no parameter-specific guidance beyond briefly mentioning WM_SETTEXT, leaving the high baseline score of 3 appropriate.

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 and resource: dispatch focusless mouse/keyboard actions. The mention of PostMessageW and SendMessageTimeoutW(WM_SETTEXT) identifies the mechanism and implies a background/foreground distinction from sibling tools like cu_click and cu_type, though it does not name those alternatives explicitly.

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 word 'focusless' implies this tool is for targeting windows without focusing them, but the description does not explicitly say when to use this instead of cu_click, cu_type, or cu_scroll, nor does it 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