Skip to main content
Glama
Sign In
Ghosthand

Ghosthand

by kumard3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

click_text

Identify and click an element using its text label; supports nth match, double-click, and stealth mode.

Instructions

Identification + interaction in one step: find the element that best matches the given text/label, then human-move the cursor to it and click. Re-reads the page if the element isn't there yet. nth picks a later match, stealth:true delivers trusted events, double double-clicks.

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": {
      "text": "<text>"
    },
    "name": "click_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
nthNo
textYes
doubleNo
stealthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.9

TDQS

A4.2/5.0
Behavior4/5

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

Discloses key behaviors: re-reads page if element missing, nth picks later match, stealth delivers trusted events, double double-clicks. Lacks info on failure handling but overall transparent given no annotations.

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?

Three sentences with front-loaded purpose, each sentence adding value with no waste.

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 a complex tool with 4 parameters and no output schema, description covers re-reading, event trust, and matching variants. Lacks details on edge cases but sufficient for typical usage.

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?

Adds meaning for nth, stealth, and double parameters, but text parameter is obvious and parameter types not described. With 0% schema coverage, description partially compensates but could be more comprehensive.

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 clearly states it combines identification and interaction in one step by finding an element matching text/label and clicking it, distinguishing it from siblings like click or find.

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?

Implicitly clear that it is for text-based identification and clicking, but lacks explicit when-to-use vs. alternatives like click or hover.

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