Skip to main content
Glama
Sign In
a11y-toolkit

a11y-toolkit

by kinti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

a11y-toolkit: Screen reader transcript

a11y_sr_transcript
Read-onlyIdempotent

Transcribe what a screen reader announces on a page, returning the linear reading order of roles, names and states so agents can review a page from a blind user's perspective.

Instructions

Screen reader TRANSCRIPT: what a blind user HEARS on this page. Walks the accessibility tree linearly and returns the announcement text with roles, names and states — the linearized reading experience, as prose an agent can READ to understand the page from a blind user's perspective. — Read-only: for structure use a11y_snapshot, for keyboard traps use a11y_keyboard. Requires Playwright. Returns JSON: {url, total, announcements [{time, politeness, role, text}] — the linearized reading order}.

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": {
      "url": "<url>"
    },
    "name": "a11y_sr_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to transcribe
langNoOutput language (en default)
browserNoBrowser engine (auto = detect the first available)
timeoutNoPage load timeout (45 default)
auth_stateNoPath to a Playwright storage_state JSON (exported session) to audit behind login — stays local

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.5.0
    • addedInput schema / properties / auth_state
      Added value: +{
+  "description": "Path to a Playwright storage_state JSON (exported session) to audit behind login — stays local",
+  "type": "string"
+}
    • addedInput schema / properties / browser
      Added value: +{
+  "description": "Browser engine (auto = detect the first available)",
+  "enum": [
+    "auto",
+    "chromium",
+    "firefox",
+    "webkit",
+    "chrome",
+    "msedge"
+  ],
+  "type": "string"
+}
  2. Addedv4.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real context beyond that: the linearized walk behavior, the Playwright dependency, and the exact return shape. It does not cover auth/permission needs beyond the schema's own auth_state note.

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

Conciseness4/5

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

Front-loaded with the core concept and well organized with em-dash-separated clauses. Slightly repetitive ('the linearized reading experience' and 'as prose an agent can READ... from a blind user's perspective' say overlapping things), but no wasted structure.

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

Completeness5/5

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

For a read-only tool with no output schema, the description supplies the return contract ({url, total, announcements [{time, politeness, role, text}]}), the dependency, and the sibling routing — everything an agent needs to invoke and interpret it.

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 all five parameters (url, lang, browser, timeout, auth_state). The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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+resource ('Screen reader TRANSCRIPT: what a blind user HEARS on this page') and explains the mechanism — walking the accessibility tree linearly. It explicitly distinguishes itself from siblings by naming a11y_snapshot and a11y_keyboard.

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?

Explicit routing: 'for structure use a11y_snapshot, for keyboard traps use a11y_keyboard.' It also flags the required dependency ('Requires Playwright'), giving the agent the conditions under which the tool applies.

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