Skip to main content
Glama

desktop_mouse_up

Releases a mouse button at the specified coordinates to complete click or drag interactions, with optional button and modifier key settings.

Instructions

agent-desktop mouse-up: Release mouse button at coordinates (fails closed in stateless mode; use mouse-click or drag)

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": {
      "xy": "<xy>"
    },
    "name": "desktop_mouse_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
xyYesAbsolute coordinates as x,y; requires --headed; write a negative value with = (--xy=-100,50)
buttonNoMouse button: left, right, middleleft
modifiersNoHeld modifiers: shift, meta, ctrl, alt (repeatable; cmd is accepted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the significant failure mode (fails closed in stateless mode), which is genuine behavioral value, but it omits what happens when no button is held, whether the release is idempotent, and whether the call reports success or silently no-ops.

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?

One compact clause, front-loaded with the action and immediately followed by the caveat and alternatives; nothing is wasted. It loses a point only because the 'agent-desktop mouse-up:' prefix largely restates the tool name.

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

Completeness3/5

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

For a three-parameter, annotation-free low-level input tool, the definition covers the critical stateful-mode caveat and defers parameter detail to a fully documented schema. It is still incomplete on the prerequisite ordering (mirroring mouse-down) and on return/failure signaling, which an agent needs to invoke it reliably.

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% and already documents the xy format, the negative-value '=' workaround, the --headed requirement, button defaults, and modifier names. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource — 'Release mouse button at coordinates' — which clearly separates it from desktop_mouse_down, desktop_mouse_click, and desktop_drag. The only weakness is that the alternatives are named informally ('mouse-click', 'drag') rather than by their exact sibling tool names.

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?

Gives an explicit when-not condition ('fails closed in stateless mode') and redirects to 'mouse-click or drag' as substitutes, which is real routing guidance. It stops short of stating the positive precondition — that a matching mouse-down must already have been issued in a stateful session — and does not give the exact sibling identifiers.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.