Skip to main content
Glama

Send input to device

device_input

Send one tap, swipe, text or key event to a running device. Coordinates are device pixels (pixel_8 is 720x1560; see profiles_list). tap: x, y. swipe: x1, y1, x2, y2, optional ms (default 300). text: text (max 500 chars). key: HOME, BACK, RECENTS, ENTER, DEL or TAB. Take a screenshot afterwards to see the effect.

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": {
      "device_id": "<device_id>",
      "type": "<type>"
    },
    "name": "device_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
msNoSwipe duration
x1No
x2No
y1No
y2No
keyNo
textNo
typeYes
device_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that exactly one event is sent, that coordinates are device pixels, the default swipe duration, text length limit, allowed key values, and the recommendation to screenshot afterward. It does not cover permission requirements, error behavior, or return semantics, which are minor remaining gaps.

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 front-loaded with the core action, then groups parameter guidance by input type in short, efficient sentences. Every sentence adds useful information with no filler.

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 an 11-parameter tool with no annotations and no output schema, the description provides enough operational detail to invoke it correctly, including coordinate semantics and post-action verification via screenshot. It could still say more about device state requirements or what a successful call returns, but the essential guidance is present.

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

Parameters5/5

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

Schema description coverage is only 9%, so the description must compensate, and it does: it maps parameters to each input type (tap, swipe, text, key), explains the optional ms default of 300, gives the text max of 500, lists valid key values, and clarifies that coordinates are in device pixels with a profile example.

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 states a specific verb and resource: send one tap, swipe, text, or key event to a running device. It clearly enumerates the supported input modes and distinguishes this from related tools by referencing profiles_list for dimensions and device_screenshot for verifying effects.

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?

Usage context is clear: it targets a running device and recommends taking a screenshot afterwards. It does not explicitly contrast when to use this versus siblings like device_run_task or device_screenshot, but the operational context is sufficiently clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources