Skip to main content
Glama

browser_accessibility

Read Chrome's native accessibility tree and return semantic DOM snapshots for Chrome and Firefox tabs to inspect accessible page state.

Instructions

Read Chrome's native accessibility tree. Snapshot provides semantic DOM state on both browsers.

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": {
      "tabId": "<tabId>"
    },
    "name": "browser_accessibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab id from browser_tabs.
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read operation but does not state what happens on a non-Chrome browser (error? empty tree?), whether the tree is paginated or truncated, or what the returned structure looks like for a tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, but the second one is the weakest: it introduces an unexplained reference to "Snapshot" and a "both browsers" claim that conflicts with the Chrome-specific first sentence, costing clarity rather than saving words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description should explain the return shape and the Chrome-only failure mode, and it does neither. For a read tool whose entire value is the returned tree, an agent cannot tell what it will receive or what limits apply.

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 100% and both parameters (tabId, browser) are documented in the schema, so the baseline is 3. The description adds nothing about how browser defaults are resolved or what the Chrome-only constraint means for the browser parameter's valid values.

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?

"Read Chrome's native accessibility tree" states a specific verb and resource, which distinguishes it from generic observation tools. The second sentence muddies scope: "Snapshot provides semantic DOM state on both browsers" reads as a reference to a sibling (browser_snapshot) but never says so explicitly, leaving ambiguity about whether this tool works on Firefox.

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 Chrome-only framing implicitly routes agents to browser_snapshot for cross-browser work, which is useful context. However, it is only implied through a vague noun ("Snapshot") rather than an explicit when-to-use/when-not statement naming the alternative.

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