wcagc-mcp

Get a full-site scan run by id

get_run

Read-onlyIdempotent

Retrieve progress and severity counts for a full-site accessibility scan run, including final failure reason once complete.

Instructions

Polls a full-site run started by scan_site — page progress, severity counts and, once terminal, a failure reason. Pro+. For a single-page scan from scan_url, use get_scan instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`runId`	Yes	The id returned by scan_site.

Output Schema

TableJSON Schema

Name	Required	Description
`run`	Yes
`standard`	Yes	The standard the checks were run against, e.g. "WCAG 2.1 AA".
`scoringGuidance`	Yes	Binding instruction for the assistant reading this result. Follow it literally.
`coverageDisclaimer`	Yes	Why this result is not a compliance verdict. Always relay it; never present a scan as proof of conformance.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedv0.1.2Jul 28, 2026

addedInput schema / properties / runId / description
```
Added value: +"The id returned by scan_site."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "coverageDisclaimer": {
+      "description": "Why this result is not a compliance verdict. Always relay it; never present a scan as proof of conformance.",
+      "type": "string"
+    },
+    "run": {
+      "additionalProperties": false,
+      "properties": {
+        "counts": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "critical": {
+                  "type": "number"
+                },
+                "minor": {
+                  "type": "number"
+                },
+                "moderate": {
+                  "type": "number"
+                },
+                "serious": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "critical",
+                "serious",
+                "moderate",
+                "minor"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "failureReason": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "code": {
+                  "type": "string"
+                },
+                "reason": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "code"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "id": {
+          "type": "string"
+        },
+        "pagesDone": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "pagesTotal": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "siteId": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "type": "string"
+        },
+        "totalViolations": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "id",
+        "status"
+      ],
+      "type": "object"
+    },
+    "scoringGuidance": {
+      "description": "Binding instruction for the assistant reading this result. Follow it literally.",
+      "type": "string"
+    },
+    "standard": {
+      "description": "The standard the checks were run against, e.g. \"WCAG 2.1 AA\".",
+      "type": "string"
+    }
+  },
+  "required": [
+    "run",
+    "coverageDisclaimer",
+    "scoringGuidance",
+    "standard"
+  ],
+  "type": "object"
+}

Addedv0.1.1Jul 25, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context beyond annotations: it is a polling operation (implies repeated calls), provides progress, severity counts, and failure reason. The 'Pro+' hint about access control is additional.

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?

Two sentences, no wasted words. First sentence defines the tool's core function, second provides a clear alternative. Information is front-loaded.

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?

The description is complete for a simple read-only poll tool with one parameter and an output schema. It explains what the tool does, what it returns, prerequisites (run started by scan_site), and distinguishes from sibling. No gaps.

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 100% and already states 'The id returned by scan_site.' The tool description reinforces this by mentioning the parameter in context ('Polls a full-site run started by scan_site — ...'). This adds value by linking the parameter to the tool's workflow.

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 clearly states the verb 'polls', the resource 'full-site run started by scan_site', and what it returns (page progress, severity counts, failure reason). It also distinguishes from the sibling tool 'get_scan' by specifying the scope (full-site vs single-page).

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?

The description explicitly says when to use ('after scan_site') and provides an alternative ('For a single-page scan from scan_url, use get_scan instead'). Also mentions 'Pro+' which indicates access tier requirements.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WCAG-Compliance/wcagc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server