Skip to main content
Glama
Sign In
Termux MCP Server

Termux MCP Server

by xlisp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tap_screen

Tap the screen at given x and y pixel coordinates to mimic a user touch. Obtain coordinates via screenshot and UI dump tools.

Instructions

Tap the screen at specific coordinates.

Use take_screenshot + dump_ui first to find the right coordinates.

Args: x: X coordinate (pixels from left) y: Y coordinate (pixels from top)

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It describes the basic action but lacks details on tap duration, immediate response, or any side effects, though for a simple tap this is minimally 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?

Extremely concise: two sentences for the main description and two lines for parameter explanations, with no redundant information.

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

Completeness5/5

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

For a simple tap action with only two parameters, the description fully explains the tool's purpose, usage context, and parameter semantics. Output schema exists, so return values need not be described.

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?

Schema coverage is 0%, but the description adds meaningful context: 'pixels from left' and 'pixels from top' clarifies unit and origin, going beyond schema types.

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 taps the screen at specific coordinates, distinguishing it from sibling tools like swipe_screen, long_press, etc., which involve different gestures.

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?

Provides explicit advice to use take_screenshot and dump_ui first to find coordinates, but does not mention when not to use this tool or alternatives for different tasks.

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