Skip to main content
Glama

net-web-media

html_accessibility_audit

Static-audit HTML for WCAG accessibility defects: missing , , alt text, form associations, empty buttons/links, and heading skips.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral load, and it does disclose one important trait: the audit is static, not a live render. It says nothing about whether it fetches remote URLs, whether it is read-only and side-effect free, how findings are ordered, or what the report contains.

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 sentence with the verb and scope front-loaded and a compact enumeration of checks. Every listed defect earns its place by defining coverage boundaries.

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?

There is no output schema, no annotations, and no parameter documentation, so the description is the only source of truth — yet it omits how input is supplied (text vs filePath, both optional) and what the audit returns. For a tool with this much unstated structure, it is under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the two parameters 'text' and 'filePath'. With zero required parameters, the mutual exclusivity and fallback behavior between inline text and a path is left entirely unexplained, so the description fails to compensate for the schema gap.

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?

The description gives a specific verb and resource ('Static-audit HTML') and then enumerates the exact defects checked (missing lang, title, alt text, label associations, empty buttons/links, heading skips). That specificity separates it cleanly from the sibling audit tools such as http_headers_security_audit.

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 word 'Static-audit' implicitly scopes it to markup-level analysis rather than rendered/JS-driven checks, which is a helpful hint. However, it never states when to choose it, when it is insufficient (e.g. runtime-only accessibility issues), or that text and filePath are alternative input sources.

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.

Resources