Skip to main content
Glama

Accessibility conformance audit

submit_accessibility_conformance_audit
Idempotent

Audit an HTML page against the WCAG 2.1 success criteria that can be decided from the markup alone — page language, title, headings, a missing alt attribute, form-field labels, link and button names, table headers, iframe titles and zoom restrictions that stop a screen reader or low-vision user — each failure named with its criterion and conformance level, plus a per-criterion pass/fail table and an overall verdict. Before shipping a page, to catch the WCAG failures a markup scan can decide deterministically. Do not choose this when you need contrast, keyboard or screen-reader testing, which needs a rendered page and a human. Example requests: Audit this HTML page for WCAG 2.1 accessibility failures. | Which WCAG success criteria does this markup fail? | Check this page for missing alt text, labels and a page language. | Run an accessibility conformance audit over this HTML.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_accessibility_conformance_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false (a job submission), and nothing in the description contradicts that. Beyond the annotations it adds real substance: which criteria are evaluated, that each failure is named with its criterion and conformance level, and that a per-criterion pass/fail table plus overall verdict is produced. It stops short of describing the job/authorization lifecycle (quote acceptance), which is left to the schema.

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 clause, then trigger, then exclusion, then examples — a sensible ordering. The trailing example list largely restates the criteria already enumerated, so it is slightly redundant, though it does aid phrasing matching.

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

Completeness4/5

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

For a tool with an output schema, the description goes further than required by sketching the failure entries and verdict table, and it clearly marks the boundary of what a markup scan can decide. The only gap is silence on the priced-job authorization flow, which the input schema documents in detail.

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 75% and the nested `inputs.html` parameter is documented in-schema, so the baseline is 3. The description adds only indirect meaning — "from the markup alone" signals that HTML text is the sole input and no URL or rendered page is accepted — but says nothing about the quote_id / authorized_by / accepted_price authorization mechanics.

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 and resource ("Audit an HTML page against the WCAG 2.1 success criteria") and then bounds the scope precisely to criteria "that can be decided from the markup alone," enumerating them: page language, title, headings, alt attributes, form labels, link/button names, table headers, iframe titles, zoom restrictions. That enumeration makes it unmistakable against the many other submit_* siblings.

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?

Gives an explicit trigger ("Before shipping a page") and an explicit exclusion ("Do not choose this when you need contrast, keyboard or screen-reader testing, which needs a rendered page and a human"), naming the reason for the boundary. Four example requests reinforce the routing decision.

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