Long-presses a specific screen coordinate on a connected iPhone, with an optional duration, to trigger context menus or press-and-hold actions.
长按屏幕坐标(点)。
| Name | Required | Description | Default |
|---|---|---|---|
| x | Yes | ||
| y | Yes | ||
| seconds | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of describing behavior, yet it says nothing about hold duration, side effects (such as a context menu or drag), device-state requirements, or failure modes. The only behavioral information is that the action is coordinate-based rather than element-based, which is already obvious from the name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of a single short sentence that is front-loaded and contains no filler. This brevity, however, crosses into under-specification: nothing is wasted, but nothing useful beyond the bare action is conveyed.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-parameter mutation-style UI tool with no annotations and no output schema, one sentence is far from sufficient. The undeclared seconds default and the unspecified coordinate format are gaps an agent would hit immediately when calling it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the schema names only the fields x, y, and seconds with no units, coordinate space, or ranges. The description adds nothing: it never mentions the seconds parameter or its default of 1, and it does not clarify whether coordinates are absolute pixels, points, or normalized values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb plus resource: long-press at a screen coordinate. That is enough to separate it from iphone_tap and iphone_tap_element, since it implies a press-and-hold. It never names those siblings, so the distinction is left implicit rather than explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no indication of when to use long press instead of iphone_tap or iphone_tap_element, nor any precondition such as the target app being foregrounded or the element being identified. The agent must guess the use case from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.