Skip to main content
Glama
Message From Aliens MCP

Message From Aliens MCP

by windlandneko

rclick

Performs a right-click at the specified x/y screen coordinates and returns the updated screen for verification.

Instructions

Right-click. Returns the screen.

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": "rclick"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.5/5.0
Behavior3/5

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

The annotations already declare non-read-only, non-idempotent, non-destructive behavior, so the description's main added value is the return contract: "Returns the screen" tells the agent it gets a refreshed view after acting. It does not disclose what the right-click actually does (opens a context menu?) or why the call is non-idempotent, which is the key behavioral unknown here.

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?

Two short, front-loaded sentences with no filler. Brevity is a virtue here, though the second sentence is doing very little work for the space it takes.

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?

A two-parameter interaction tool with no output schema and no parameter documentation needs the description to explain the coordinate space and what the returned screen contains; it does neither. The definition is well short of what an agent needs to call this correctly.

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

Parameters1/5

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

Schema description coverage is 0% and the description mentions neither parameter. The tight bounds (x 0-23, y 0-8) strongly imply a fixed 24x9 grid but the description never confirms the coordinate system, origin, or units, leaving both required parameters semantically undocumented.

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

Purpose3/5

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

"Right-click" names a specific action and the "right" qualifier distinguishes it from the sibling click tool, but the description never says what surface is being right-clicked (screen grid, cell, element) or that x/y address a coordinate. The agent gets the verb but must infer the object.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of when a right-click is appropriate versus click, note, or render, and no note that it opens a context menu requiring a follow-up action. The only hint is the implicit left/right contrast with the sibling name.

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