Skip to main content
Glama
Sign In
Computer Use MCP Server

Computer Use MCP Server

by SebastianBaltes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

computer_triple_click

Select a line of text by triple-clicking at specified screen coordinates.

Instructions

Triple-click at the given coordinates (select a line of text). The display is 1429x804 pixels (scaled from 1920x1080). All coordinates are in the scaled coordinate space.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "computer_triple_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the behavioral effect (line selection) and the coordinate system (scaled space) and display resolution. However, it does not mention any other behavioral traits like mouse movement, focus requirements, or return values, but for a simple click tool this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with two sentences covering purpose, effect, and coordinate context. Every sentence earns its place with no redundancy or wasted words.

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 simple action tool without output schema, the description covers the essential: what it does, the coordinate system, and the display resolution. It does not mention return behavior (likely nothing returned), but for this tool type that is acceptable. It is sufficiently complete for an AI agent to use correctly.

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?

Input schema covers 100% of parameters with basic descriptions. The description adds value by stating 'All coordinates are in the scaled coordinate space' and providing the display resolution, which clarifies the coordinate system beyond the schema's simple 'X coordinate' and 'Y coordinate'.

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 'Triple-click at the given coordinates (select a line of text).' This specifies the action (triple-click), the target (coordinates), and the effect (select a line). It effectively distinguishes from siblings like double_click (word selection) and left_click (cursor placement).

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 implies when to use the tool by noting the selection outcome: 'select a line of text.' While not explicit about when not to use or alternative tools, the context of sibling tools (double_click, left_click) makes the usage clear. A more explicit guideline would elevate to 5.

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