Skip to main content
Glama

qq_click

Simulates a mouse click at specified coordinates on the QQ client window to trigger buttons, menus, or messages, then returns a fresh screenshot for verifying the result.

Instructions

Click on the QQ client window (coordinates as seen in the last qq_screenshot / qq_login image). Returns a fresh screenshot.

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

Input Schema

NameRequiredDescriptionDefault
xYesX in the screenshot
yYesY in the screenshot
buttonNoMouse buttonleft
doubleNoDouble-click
relative_to_windowNoCoordinates are relative to the QQ window screenshot (default) or the full screen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare that this is not read-only, is open-world, and is non-destructive. The description adds that a fresh screenshot is returned, but it does not disclose failure behavior, focusing requirements, or other side effects of the click.

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 a single compact sentence with the main action and coordinate source front-loaded. The return value is stated immediately after, with no wasted wording.

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?

Given the annotations, complete parameter schema, and absence of an output schema, the definition covers the essential purpose, coordinate reference, and return behavior. It is slightly thin on failure modes and alternative-click scenarios, but otherwise complete for a UI click tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the five parameters are fully documented in the schema. The description reinforces that x and y are relative to the last screenshot/login image, but it adds no information about button, double-click, or relative_to_window beyond the schema.

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 states a specific verb and resource: clicking on the QQ client window. It also clarifies the coordinate source and that a fresh screenshot is returned. It does not explicitly distinguish itself from the sibling inline-keyboard click tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The mention of coordinates from the last qq_screenshot or qq_login image implies a workflow and when the tool can be used. However, there is no explicit when-to-use guidance versus alternatives such as click_inline_keyboard_button or qq_type.

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