Skip to main content
Glama
oetiker

MCPretentious

by oetiker

mcpretentious-mouse

Send mouse events (press, release, drag) to a terminal using SGR protocol. Control cursor position, button clicks, and scroll actions with optional modifier keys.

Instructions

Send mouse events to a terminal using SGR mouse protocol.

This tool provides direct control over mouse events following the terminal's SGR (Select Graphic Rendition) mouse protocol.

EVENTS:
- 'press': Mouse button press event
- 'release': Mouse button release event  
- 'drag': Mouse movement with button held down

BUTTONS (use names or button-N format):
Named buttons:
- 'left': Left mouse button
- 'middle': Middle mouse button
- 'right': Right mouse button
- 'scrollUp': Scroll wheel up
- 'scrollDown': Scroll wheel down

Direct button codes:
- 'button-0' through 'button-127': Direct SGR button codes
- Common codes: 0=left, 1=middle, 2=right, 64=scrollUp, 65=scrollDown

MODIFIERS (optional, default to false):
- shift: Hold shift key during event
- alt: Hold alt/option key during event
- ctrl: Hold control key during event

COORDINATES:
- x and y are 0-based character positions (column, row)
- The protocol will convert to 1-based coordinates internally

EXAMPLES:
- Left click at (10,5): event='press', button='left', x=10, y=5, then event='release' with same coordinates
- Drag from (5,5) to (15,10): event='press' at (5,5), event='drag' at (15,10), event='release' at (15,10)
- Scroll up at (20,8): event='press', button='scrollUp', x=20, y=8 (no release needed for scroll)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
terminalIdYesThe terminal ID to send mouse events to
eventYesMouse event type: 'press' for button down, 'release' for button up, 'drag' for movement with button held
xYesX coordinate (column position, 0-based)
yYesY coordinate (row position, 0-based)
buttonYesMouse button: named ('left', 'middle', 'right', 'scrollUp', 'scrollDown') or direct code ('button-0' through 'button-127')
shiftNoShift key modifier
altNoAlt/Option key modifier
ctrlNoControl key modifier
Behavior4/5

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

No annotations are provided, so the description bears full responsibility. It explains the SGR protocol, coordinate conversion from 0-based to 1-based, and modifier optionality. It does not disclose any destructive or side effects, but for a mouse event tool this is reasonable.

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 well-structured with clear sections (EVENTS, BUTTONS, MODIFIERS, COORDINATES, EXAMPLES) and is front-loaded with the main purpose. It is somewhat lengthy but each part serves a purpose; very few redundant sentences.

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?

For a tool with moderate complexity, no output schema, and no annotations, the description covers all necessary aspects: input parameters, protocol details, and usage examples. It lacks explicit return value info but that is acceptable for an action tool.

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

Parameters4/5

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

With 100% schema coverage, baseline is 3. The description adds significant value by explaining button code ranges (button-0 to button-127), listing common codes, clarifying modifier defaults, and providing coordinate conversion details. Examples further enhance understanding.

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 tool's purpose: 'Send mouse events to a terminal using SGR mouse protocol.' It details events, buttons, modifiers, and coordinates, distinguishing it from siblings like mcpretentious-type or mcpretentious-read.

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 examples and explains when to use the tool for mouse interactions. However, it does not explicitly state when not to use it or mention alternatives among sibling tools, which slightly reduces clarity for an agent deciding between tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oetiker/MCPretentious'

If you have feedback or need assistance with the MCP directory API, please join our Discord server