Skip to main content
Glama
Sign In
Cat Burglar

Cat Burglar

by DrMkdaddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Click

click

Triggers an element by ref, selector, text, or role+name and returns a compact change observation, reducing the need for follow-up snapshots.

Instructions

Click an element. Target one of: ref (preferred), selector, text, or role+name. Humanized mouse movement is used by default. Returns a compact change observation so you rarely need a second snapshot.

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

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot, e.g. e12. Preferred over selectors.
nameNoAccessible name to combine with role.
roleNoARIA role, e.g. button, link, textbox, checkbox, combobox.
textNoVisible text to match (first match wins).
exactNoRequire exact text/name match.
buttonNo
confirmNoConfirm a high-impact action when the server policy is ask.
observeNoReturn a compact change observation after the action (default true).
humanizeNo
selectorNoCSS selector (use when no ref is available).
click_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false. The description adds real behavioral context beyond that: humanized mouse movement is on by default, and a compact change observation is returned so a second snapshot is rarely needed. It does not mention side effects like navigation or that confirmation may be required under server policy, which keeps it from a 5.

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 short sentences, action first, then targeting options, then behavior and return value. No filler and nothing is buried.

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 an 11-parameter mutation tool with no output schema, the description covers targeting strategy, default behavior, and the shape of the return (compact change observation). It leaves out what happens on navigation-triggering clicks and when confirm applies, which are the remaining gaps.

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

Parameters4/5

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

Schema coverage is 73%, so the schema already carries much of the parameter meaning (ref preferred, exact match, button enum, confirm, observe default true). The description adds the priority ordering among targeting modes and restates the humanize default, giving the agent guidance the schema only implies field-by-field.

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?

"Click an element" is a specific verb+resource, and the enumeration of targeting strategies (ref, selector, text, role+name) makes clear what kind of element interaction this is. It does not explicitly separate itself from near-neighbours like hover, type, or fill, so it falls just short of the top mark.

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 description gives intra-tool guidance ("ref (preferred)... use selector when no ref is available" via schema) but no when-to-use-this-vs-another-tool guidance, e.g. when to click versus type/fill or press. Usage is implied by the element-targeting rules rather than stated against alternatives.

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