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. Returns: pass (bool), violations[] with id/impact/help/help_url/nodes_affected.

Input Schema

Name	Required	Description
`url`	No	Live, fetchable http(s) URL to audit.
`html`	No	Raw HTML source to audit instead of fetching a URL.
`language`	No	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.

Output Schema

Name	Required	Description	Default
`pass`	Yes
`engine`	No
`status`	No
`violations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

removedInput schema / anyOf

Removed value: -[
-  {
-    "required": [
-      "url"
-    ]
-  },
-  {
-    "required": [
-      "html"
-    ]
-  }
-]

addedInput schema / minProperties
```
Added value: +1
```

Changed5 schema fields changedOct 1, 2026

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"
```

Changed1 schema field changedSep 27, 2026

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"
+}

Changed2 schema fields changedSep 12, 2026
- 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"
+]
```

Changed8 schema fields changedAug 25, 2026

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"
+}

First observedAug 11, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With annotations already covering read-only, idempotent, open-world and non-destructive behavior, the description goes well beyond them: it discloses the testing engine, determinism, the error-instead-of-pass failure contract, and a $0.05 per-call cost. That cost and the fail-safe semantics are traits an agent cannot recover from the structured fields.

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?

Three dense sentences, front-loaded with the purpose and standard, then behavior, then cost and return shape — nothing is wasted. The trailing "Returns: pass (bool), violations[]..." slightly duplicates the existing output schema, which keeps it from a 5.

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 three-param audit tool with full schema coverage, an output schema, and rich annotations, the description still supplies the engine, cost, determinism and failure semantics an agent needs before spending money on a call. Nothing material is missing.

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 100%, so url, html and language are all documented at source, and the description adds little beyond restating "live URL or raw HTML." It does not explain the minProperties=1 either/or relationship or what the language tag affects, leaving the schema to do the work — baseline 3.

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?

States a specific verb+resource ("Website accessibility audit") and pins the exact standard (WCAG 2.1 A/AA) plus the engine (axe-core in a headless browser), which cleanly separates it from audit_seo, audit_performance and audit_security. It never names those siblings explicitly, so the differentiation is inferable from the domain label rather than stated.

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?

"Any live URL or raw HTML" tells the agent exactly which input modes are accepted, and the deterministic-rules note clarifies that a failed run surfaces an error rather than a false pass. It gives no explicit exclusion or pointer to audit_bundle when the agent wants accessibility combined with other checks, so the sibling routing is only implied.

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

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

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.