Skip to main content
Glama
Sign In
HarmonyOS MCP Server

HarmonyOS MCP Server

by XixianLiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

long_click

Perform a long click at a specified coordinate on the screen. Useful for invoking context menus or activating long-press actions on HarmonyOS devices.

Instructions

long 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": "long_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
centerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description gives minimal behavioral insight. It does not disclose what happens after a long click (e.g., context menu, press-and-hold), error handling, or whether it blocks until release.

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?

The description is concise but includes an 'Args' section that is redundant with the single parameter. Still, it is front-loaded with the action statement.

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?

Given the output schema exists (but not shown), the description may be adequately complete for a simple action, but it lacks any context about return values or side effects.

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?

The description adds format guidance for the 'center' parameter with a concrete example '(x, y)' and sample '(227, 168)', which goes beyond the schema's type-only definition. However, it could specify coordinate system origin or bounds.

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?

Clearly states it performs a 'long click' at a given coordinate, distinguishing it from the sibling 'click' tool. The verb (long click) and resource (coordinate) are specific and unambiguous.

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 like 'click' or 'swipe'. No conditions, prerequisites, or exclusions are mentioned.

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