Skip to main content
Glama
snayyar00

@webability/mcp

by snayyar00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List accessibility rules

get_rules
Read-onlyIdempotent

List accessibility rules from axe-core and WebAbility with filters by rule, tag, engine, or fixability, and see each rule's fix template so you can pick auto-fixable ones before scanning.

Instructions

List accessibility rules from both engines — axe-core (104) and the WebAbility detectors (90+) — with optional filters. Every rule carries fixability (mechanical | contextual | visual) and a fix op template, so you can pick the rules worth auto-fixing before scanning. Returns ruleId, engine, description, help, helpUrl, tags/wcag, fixability, fix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ruleNoOnly rules whose id contains these whole words (e.g. "link" → link-name, skip-link, not blink; "color-contrast"; case and -/_ insensitive). Also accepted: ruleId, id, query.
tagsNoaxe tag filter (e.g. ["wcag2aa"], ["best-practice"], ["cat.aria"]; a category also works without "cat."). WebAbility rules match on their WCAG criterion tag (e.g. "wcag143"). An unknown tag or category is an error that lists the valid ones.
engineNoWhich engine's rules to list (default all)
fixabilityNoOnly rules of this fixability tier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.7.0
    • addedInput schema / properties / engine
      Added value: +{
+  "description": "Which engine's rules to list (default all)",
+  "enum": [
+    "all",
+    "axe",
+    "webability"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / fixability
      Added value: +{
+  "description": "Only rules of this fixability tier",
+  "enum": [
+    "mechanical",
+    "contextual",
+    "visual"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / rule
      Added value: +{
+  "description": "Only rules whose id contains these whole words (e.g. \"link\" → link-name, skip-link, not blink; \"color-contrast\"; case and -/_ insensitive). Also accepted: ruleId, id, query.",
+  "type": "string"
+}
    • changedInput schema / properties / tags / description
      Previous value: -"Filter by tags (e.g. [\"wcag21aa\"], [\"best-practice\"], [\"cat.aria\"])"New value: +"axe tag filter (e.g. [\"wcag2aa\"], [\"best-practice\"], [\"cat.aria\"]; a category also works without \"cat.\"). WebAbility rules match on their WCAG criterion tag (e.g. \"wcag143\"). An unknown tag or category is an error that lists the valid ones."
  2. First observedv1.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: rules span two engines, each carries a fixability tier and a fix op template, which tells the agent what differentiates the output. It omits ordering/pagination, keeping it at a 4 rather than 5.

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 purpose, then the value proposition and return fields in two tight sentences. The trailing return-field enumeration is slightly list-like, but it is useful given there is no output schema, so it earns its space.

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, the description usefully enumerates returned fields (ruleId, engine, tags/wcag, fixability, fix) and explains both engines and the filter dimensions. Minor gaps remain around result ordering or size limits, but nothing essential for correct invocation 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% and the schema descriptions are detailed (whole-word matching, tag formats, engine enum semantics), so the schema does the heavy lifting. The description only refers to 'optional filters' generically and adds no syntax or format meaning beyond the schema, matching the baseline 3.

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 opens with a specific verb and resource ('List accessibility rules') and scopes it precisely to two named engines with concrete counts (axe-core 104, WebAbility 90+). An agent can immediately distinguish this rule-catalog tool from scanning siblings like scan_page or check_aria.

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?

It gives a clear use context ('pick the rules worth auto-fixing before scanning'), which implies when to call it ahead of a scan. However, it never names an alternative tool or an explicit when-not-to-use case, so routing is inferred rather than stated.

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

Deploy Server

Other Tools