Skip to main content
Glama

Focusable elements inside aria-hidden regions

bpj_html_hidden_focusable
Read-onlyIdempotent

Locate native interactive or nonnegative tabindex elements in explicitly aria-hidden source subtrees.

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": {
      "text": "<text>"
    },
    "name": "bpj_html_hidden_focusable"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuine scope detail — only 'explicitly aria-hidden' subtrees count, and only native elements or nonnegative tabindex values are flagged — but says nothing about what findings look like, whether line numbers or snippets are returned, or what it cannot detect (e.g. CSS-driven hiding).

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?

A single front-loaded sentence with no filler; every qualifier ('native', 'nonnegative tabindex', 'explicitly aria-hidden') narrows the scope meaningfully. Nothing is redundant with the title or annotations.

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?

For a one-parameter read-only check this is close, and the annotations carry the behavioral contract. However, with no output schema, the description should indicate what the tool reports back (element identities, counts, locations) — that gap is real for an agent deciding whether this call answers its question.

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 0%, and the description does not discuss the single 'text' parameter at all beyond implying it holds HTML source. The schema's own title 'Source text' and maxLength of 6000 make the parameter largely self-explanatory, but the description does not compensate for the missing coverage or clarify whether a full document or a fragment is expected.

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 ('Locate') and a precise resource: native interactive or nonnegative-tabindex elements within explicitly aria-hidden source subtrees. The scope qualifiers (native, nonnegative tabindex, explicitly aria-hidden) distinguish it from siblings like bpj_html_positive_tabindex without needing to name them.

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

Usage Guidelines2/5

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

The description never says when to reach for this check versus related audits such as bpj_html_positive_tabindex or bpj_html_aria_reference_targets, nor does it state any preconditions about the input. Usage is only inferable from the tool name and the accessibility-audit family it belongs to.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.