Skip to main content
Glama
Sign In
HarmonyOS MCP Server

HarmonyOS MCP Server

by XixianLiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

click

Click at a specified screen coordinate on a HarmonyOS device. Provide coordinates as "(x, y)" to trigger the action.

Instructions

click the given coordinate Args: center: a string like "(x, y)", sample: "(227, 168)"

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": {
      "center": "<center>"
    },
    "name": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
centerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It fails to disclose basic behaviors like what happens with out-of-bounds coordinates, click duration, or whether it's a single tap, leaving significant ambiguity.

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?

Short and front-loaded with the core action. The Args structure is neatly formatted, though the description is very brief.

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?

For a simple click tool, the description is adequate but misses key context: coordinate system origin (likely screen coordinates), units (pixels), and whether the action waits for a result. Output schema exists but return behavior is not 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?

Provides explicit format and example for the 'center' parameter ('(x, y)' format), which adds significant meaning beyond the schema's bare string type. Schema coverage is 0%, so this compensation is critical.

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 clearly states the action (click) and the target (given coordinate). It effectively distinguishes from sibling tools like long_click and swipe by specifying coordinate input.

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?

No guidance on when to use this tool versus alternatives (e.g., long_click, tap by UI element). Missing context for appropriate use.

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