Skip to main content
Glama

browser_accessibility_basic

Read-onlyIdempotent

Run read-only heuristic accessibility checks on the current approved browser page to spot common issues quickly, noting it is not a full axe-core audit.

Instructions

Read-only heuristic accessibility checks in the current approved browser page; not a complete axe-core audit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that results are heuristic rather than exhaustive, which is valuable expectation-setting, but it leaves 'approved browser page' undefined and says nothing about what checks run or what is returned.

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 the scope first and the caveat second. Every clause carries meaning and there is no filler.

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?

With no parameters and no output schema, the description is the only source of expectations about results, and it says little beyond 'heuristic'. An agent does not learn what categories of issues are reported or what 'approved' means for page eligibility.

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?

The tool takes zero parameters, so the baseline is 4. Nothing in the input schema needs disambiguation and the description correctly implies the tool operates on the already-open page state.

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 names a specific verb+resource (heuristic accessibility checks) and scopes it to the current approved browser page. It also carves out a boundary against a fuller axe-core audit, which implicitly separates it from browser_axe_audit, though it never names that sibling directly.

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

Usage Guidelines4/5

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

The clause 'not a complete axe-core audit' gives a clear selection condition: use this for quick heuristic reads and reach for the axe audit when completeness matters. The alternative is implied rather than named, and no explicit when-not-to-use case is stated.

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