Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aria Click

aria_click

Click an ARIA element by its index to perform semantic, mouse-free interactions; get the index from an ARIA snapshot or text search first.

Instructions

Click ARIA element by idx (zero mouse, semantic). Always prefer over click_at. Get idx from aria_snapshot or find_by_text.

Ex: aria_click('t0', 3) → {"ok":true}

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": {
      "tab_id": "<tab_id>",
      "idx": "<idx>"
    },
    "name": "aria_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
idxYes
tab_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully adds 'zero mouse, semantic' and an example success response, but does not describe side effects, visibility requirements, error conditions, or permission/auth needs for a mutation tool.

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 compact sentences plus a minimal example. Purpose, alternative, prerequisite, and return shape are all front-loaded with no wasted text.

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?

Output schema exists and the example reinforces it, but with no annotations the description should say more about mutation side effects and failure modes. It remains minimum viable for a simple click tool with minor gaps around `tab_id` and behavioral expectations.

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 coverage is 0%, so the description must explain both parameters. It usefully explains `idx` (from `aria_snapshot`/`find_by_text`) and the example clarifies argument order, but does not explicitly define `tab_id` as the target browser tab.

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?

States a specific verb and resource ('Click ARIA element by idx') and explicitly distinguishes itself from the coordinate-based sibling `click_at`. An agent can identify the operation and scope immediately.

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

Usage Guidelines5/5

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

Explicitly says 'Always prefer over `click_at`' and tells where to obtain the required index from `aria_snapshot` or `find_by_text`. This covers when to use it and the prerequisite data source.

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