Skip to main content
Glama
Message From Aliens MCP

Message From Aliens MCP

by windlandneko

click

Performs a left-click at the specified grid coordinates and returns the updated screen, letting you interact with game elements during play.

Instructions

Left-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": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral fact — that the current screen is returned after the click — but does not explain that clicking mutates UI state or what happens if the target is empty, which matters for a non-idempotent interaction.

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?

Two terse sentences, front-loaded with the action and followed by the return value. Nothing is padded or circular.

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?

There is no output schema, and the description does disclose that a screen image is returned, which is the key post-condition. However, for a tool whose only parameters are an undocumented coordinate pair, the description leaves the agent guessing about the coordinate system.

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

Parameters2/5

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

Schema description coverage is 0%, so the burden is on the description to explain x and y, and it offers nothing. The min/max ranges (0-23, 0-8) hint at a coordinate grid, but the description never says what coordinate space is used or what is at those positions.

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 names a specific verb and input mode ("Left-click") and states a result ("Returns the screen"), which implicitly separates it from the sibling rclick. It stops short of explicitly contrasting the two, so an agent must infer that right-click lives elsewhere.

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, no exclusion of alternatives, and no prerequisite context. The agent is told what the tool does but nothing about when this is the correct choice versus rclick or render.

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