Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getAccessibilityFindings

Retrieve accessibility scan findings by run ID, including failing WCAG A/AA rules, affected elements and fixes, manual-review checks, best practices, and changes since the previous scan.

Instructions

Read the findings of an accessibility scan: failing WCAG A/AA rules with the elements (CSS selector, HTML, how to fix), checks that need human review, best-practice recommendations, and what is new or resolved since the previous scan.

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": {
      "runId": "<runId>"
    },
    "name": "getAccessibilityFindings"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesID of the accessibility run.
elementsPerRuleNoFailing elements listed per rule (default 5, max 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well on output content and discloses one genuine behavioral trait — that results include a diff against the previous scan ('what is new or resolved') — but says nothing about permissions, pagination, rate limits, or behavior when the run is still in progress or has no prior scan to diff against.

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?

A single front-loaded sentence that leads with the verb and resource before listing the payload categories, with no filler or hedging. It is dense but the comma-separated enumeration stays readable, though the list could have been broken out for faster scanning.

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?

With no output schema and no annotations, the description compensates by describing the return payload in detail — failing rules, per-element evidence, manual-review checks, recommendations, and scan deltas — which is what an agent most needs here. The main remaining gap is the absence of any prerequisite or error-condition context for the required runId.

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 description coverage is 100%, with runId and elementsPerRule both documented in the schema, so the baseline of 3 applies. The description adds no parameter-level meaning beyond the schema: it never mentions that elementsPerRule controls how many failing elements are listed per rule, nor any format or constraint detail for runId.

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?

The description opens with a specific verb and resource ('Read the findings of an accessibility scan') and then enumerates exactly what findings means: failing WCAG A/AA rules, elements with CSS selector/HTML/fix, human-review checks, best-practice recommendations, and new/resolved deltas. That is far more than a restatement of the name and lets an agent tell it apart from getAccessibilityRuns and getAccessibilityTests. It stops short of explicitly naming those siblings, which is the only thing keeping it from a 5.

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?

Usage is only implied: the required runId parameter and the phrase 'since the previous scan' suggest this is called after a scan run exists, presumably using an ID obtained from getAccessibilityRuns. There is no explicit when-to-use/when-not-to-use statement and no alternative tool is named for cases where the agent wants raw run metadata instead of findings. An agent can infer the workflow but is given no routing guidance.

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