Skip to main content
Glama

Click on the open page

tor_click

Clicks a page element by CSS selector or visible text after browsing with tor_browse and returns the resulting page.

Instructions

Click an element on the page opened by tor_browse, by CSS selector or by visible text. Returns the resulting page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tor_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoVisible text of the link or button
selectorNoCSS selector

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and openWorldHint=true, so an agent knows this mutates external state. The description adds one useful behavioral fact, that it returns the resulting page, implying navigation may occur, but it does not cover what happens when a selector matches several elements or when neither parameter is supplied.

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 with the action and targeting methods front-loaded and the return value last. Nothing is redundant or padded.

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?

The tool has two parameters, neither of which is required, which creates real ambiguity about which one to supply and what happens if neither is supplied, and the description addresses none of that. Since no output schema exists, the single sentence about returning the resulting page is the bare minimum for a mutating, open-world 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 schema already documents both parameters. The description only restates that targeting can be by CSS selector or by visible text, adding the implied choice between the two but no format or precedence details beyond the schema; baseline 3 applies.

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 names a specific verb (click) and resource (an element on the page opened by tor_browse), and it names the two targeting mechanisms, CSS selector or visible text. It clearly separates the tool from siblings like tor_browse (which opens the page) and tor_type (which enters text).

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?

It supplies the operating context: this acts on the page already opened by tor_browse, which tells the agent the prerequisite. It gives no explicit exclusions or alternatives, such as tor_type for form entry or how to proceed when no page is open, so guidance is clear but incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.