mya11yreport-mcp

Overview Schema Source Related Servers Discussions Admin

Click element

click

Clicks a UI element after waiting for it to be visible and actionable. Target elements using CSS selectors or accessibility-first locators like getByRole or getByText.

Instructions

Clicks an element in the session page. Auto-waits for the element to be visible, stable, and actionable. Targets support CSS selectors or accessibility-first locators (getByRole, getByText, getByLabel, ...).

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

Input Schema

Name	Required	Description
`target`	Yes	How to locate the element: {"selector": "#id"} or {"fn": {"name": "getByRole", "args": ["button", {"name": "Sign in"}]}}.
`sessionId`	Yes	Session id returned by start_session. Required on every stateful tool call.
`timeoutMs`	No	Action timeout in milliseconds (default 10000).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Sep 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It adds useful transparency by stating that the tool auto-waits for the element to be visible, stable, and actionable. However, it does not disclose possible side effects such as navigation, page changes, or failure behavior on timeout, so coverage is partial.

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 tight sentences place the action first, then the key behavioral guarantee, then the targeting options. There is no filler, repetition of schema details, or unnecessary context.

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?

The combination of a rich parameter schema and this focused description covers the core knowledge an agent needs to call the tool correctly. The main gaps are the lack of alternative routing to state-change siblings and no statement of return/error behavior, but neither is critical for a straightforward click action.

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 sessionId, target, and timeoutMs in detail. The description adds only a light framing around CSS selectors and accessibility-first locators, which largely mirrors the schema's anyOf structure. It meets the baseline but does not add significant meaning beyond the schema.

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?

The description opens with a specific verb and resource: 'Clicks an element in the session page.' It clearly identifies both the action and the target context. However, it does not explicitly differentiate from sibling state-change tools such as check, uncheck, or select_option, so differentiation is mostly implicit.

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 auto-wait behavior and supported locator types suggest when the tool is appropriate, but the description gives no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives like check/uncheck for checkbox states or select_option for dropdowns, leaving the routing decision to inference.

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