Skip to main content
Glama

HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News

Accessibility audit (WCAG 2.1 A/AA)

audit_wcag
Read-onlyIdempotent

Website accessibility audit (a11y, WCAG compliance check): WCAG 2.1 level A and AA conformance of any live URL or raw HTML, tested with axe-core in a real headless browser. Returns every violation with rule id, impact, help text and affected node count. Deterministic rules; a check that cannot run returns an error, never a pass. $0.05 per call.

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

Input Schema

NameRequiredDescriptionDefault
urlNo
htmlNo
languageNo

Output Schema

NameRequiredDescriptionDefault
passYes
engineNo
statusNo
violationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / html / description
      Removed value: -"Raw HTML source to audit instead of fetching a URL."
    • removedInput schema / properties / language / description
      Removed value: -"Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable text of the findings is returned in this language; rule ids, severities, URLs and numbers are untouched. Default: English."
    • removedInput schema / properties / language / examples
      Removed value: -[
      -  "ja"
      -]
    • removedInput schema / properties / url / description
      Removed value: -"Live, fetchable http(s) URL to audit."
    • removedInput schema / properties / url / examples
      Removed value: -[
      -  "https://example.com"
      -]
    • removedInput schema / title
      Removed value: -"Live URL or raw HTML to audit"
  2. Changed2 schema fields changed
    • removedInput schema / anyOf
      Removed value: -[
      -  {
      -    "required": [
      -      "url"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "html"
      -    ]
      -  }
      -]
    • addedInput schema / minProperties
      Added value: +1
  3. Changed5 schema fields changed
    • removedOutput schema / properties / pass / description
      Removed value: -"Whether every rule in this dimension passed."
    • removedOutput schema / properties / status / description
      Removed value: -"Present only on a completed audit."
    • removedOutput schema / properties / violations / items / properties
      Removed value: -{
      -  "help": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "help_url": {
      -    "format": "uri",
      -    "type": "string"
      -  },
      -  "id": {
      -    "description": "axe-core rule id.",
      -    "type": "string"
      -  },
      -  "impact": {
      -    "description": "axe-core impact level.",
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "nodes_affected": {
      -    "minimum": 0,
      -    "type": "integer"
      -  }
      -}
    • removedOutput schema / properties / violations / items / required
      Removed value: -[
      -  "id"
      -]
    • removedOutput schema / properties / violations / items / type
      Removed value: -"object"
  4. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable text of the findings is returned in this language; rule ids, severities, URLs and numbers are untouched. Default: English.",
      +  "examples": [
      +    "ja"
      +  ],
      +  "maxLength": 35,
      +  "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{2,8})*$",
      +  "type": "string"
      +}
  5. Changed2 schema fields changed
    • changedOutput schema / properties / violations / items / properties / help / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / violations / items / properties / impact / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  6. Changed8 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "url"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "html"
      +    ]
      +  }
      +]
    • changedInput schema / properties / html / description
      Previous value: -"Raw HTML to audit instead of a URL"New value: +"Raw HTML source to audit instead of fetching a URL."
    • changedInput schema / properties / url / description
      Previous value: -"Live URL to audit"New value: +"Live, fetchable http(s) URL to audit."
    • addedInput schema / properties / url / examples
      Added value: +[
      +  "https://example.com"
      +]
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / title
      Added value: +"Live URL or raw HTML to audit"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "properties": {
      +    "engine": {
      +      "const": "axe-core",
      +      "type": "string"
      +    },
      +    "pass": {
      +      "description": "Whether every rule in this dimension passed.",
      +      "type": "boolean"
      +    },
      +    "status": {
      +      "const": "ok",
      +      "description": "Present only on a completed audit.",
      +      "type": "string"
      +    },
      +    "violations": {
      +      "items": {
      +        "properties": {
      +          "help": {
      +            "type": "string"
      +          },
      +          "help_url": {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "axe-core rule id.",
      +            "type": "string"
      +          },
      +          "impact": {
      +            "description": "axe-core impact level.",
      +            "type": "string"
      +          },
      +          "nodes_affected": {
      +            "minimum": 0,
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "id"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "pass"
      +  ],
      +  "type": "object"
      +}
  7. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world. The description adds genuinely new behavioral facts beyond them: real headless browser, deterministic rules, a fail-closed policy ("a check that cannot run returns an error, never a pass"), and a $0.05 per-call cost. That fail-closed guarantee and the pricing are precisely the traits annotations cannot express, though nothing is said about rate limits or latency.

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?

Three dense sentences, fully front-loaded: what it is, how it runs and what it returns, then the guarantee and price. No filler, and the synonym cluster ("a11y, WCAG compliance check") is packed parenthetically rather than costing a sentence.

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?

An output schema exists, so the return-value sentence is extra value rather than a necessity. For a read-only audit tool the safety, engine, determinism, and cost story is complete; the remaining gap is the undocumented language parameter and the one-of url/html constraint.

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?

Schema description coverage is 0% for 3 parameters, so the description must compensate: it distinguishes the url and html input modes ("any live URL or raw HTML"), which maps to two of the three params. It says nothing about the language parameter or about the schema's minProperties:1 constraint that makes exactly-one-of the real calling rule.

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?

Names a specific verb+resource ("Website accessibility audit") plus the exact standard (WCAG 2.1 level A and AA) and the engine (axe-core). The a11y/WCAG synonym pair and the explicit input scope ("any live URL or raw HTML") let an agent separate it from audit_performance, audit_seo, and audit_security without opening a schema.

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?

Implies the use case clearly (WCAG conformance checking) and states the two accepted input modalities, but gives no explicit when-not guidance and does not route the agent to or away from siblings such as audit_bundle. Usage is inferable rather than stated.

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.