Skip to main content
Glama
Sign In
Theseus

Theseus

by ywapom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

click

Activates a webpage control by its visible text or label; use index-based targeting when available.

Instructions

Click a control by its visible text or label. Prefer click_index.

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

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: not whether the click waits for the element, what happens on ambiguous or missing matches, or whether the click can navigate away or trigger irreversible actions. Only the addressing mechanism is explained.

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?

Two short sentences, zero waste, with the primary action stated first and the alternative immediately after. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be described. But for a UI-mutating action tool with no annotations, the definition omits the post-click behavior and error/ambiguity handling that an agent needs to invoke it confidently.

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?

The single parameter 'target' has 0% schema description coverage, so the description must compensate. 'By its visible text or label' does give useful semantics for target, but it leaves open matching rules (exact vs substring, case sensitivity) and the failure mode for multiple matches.

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?

States a specific verb (Click) and a specific addressing scheme (by visible text or label), which tells an agent exactly how the target is resolved. It is distinguishable from click_index, though the difference is only implied by the 'prefer' note rather than spelled out.

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?

'Prefer click_index' explicitly names the sibling alternative and signals the default choice, which is real routing guidance. However, it never states the condition under which this tool is the right one (e.g. only when no index is known) or what to do if the text matches multiple controls.

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