Skip to main content
Glama

webability

by io.github.snayyar00
OverviewDiscussionsAdmin

List accessibility rules

get_rules
Read-onlyIdempotent

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

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)
contextNoExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
llm_modelNoThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
fixabilityNoOnly rules of this fixability tier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
-  "type": "string"
-}
    • changedInput schema / properties / rule / description
      Previous value: -"Only rules whose id contains this text (e.g. \"color-contrast\", \"label\"; case and -/_ insensitive). Also accepted: ruleId, id, query."New value: +"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."
    • changedInput schema / properties / tags / description
      Previous value: -"axe tag filter (e.g. [\"wcag21aa\"], [\"best-practice\"], [\"cat.aria\"]). WebAbility rules match on their WCAG criterion tag (e.g. \"wcag143\")."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. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "context",
-  "llm_model"
-]New value: +[]
  3. Changed1 schema field changed
    • addedInput schema / properties / rule
      Added value: +{
+  "description": "Only rules whose id contains this text (e.g. \"color-contrast\", \"label\"; case and -/_ insensitive). Also accepted: ruleId, id, query.",
+  "type": "string"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral value beyond that: rule counts per engine, the three fixability tiers with their meaning, the presence of a fix op template, and the returned fields — enough for an agent to know what it gets back before calling.

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, both front-loaded: the first names the resource, both engines and the counts, the second explains the payload. No filler, and the payoff ('pick the rules worth auto-fixing before scanning') lands early.

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?

With no output schema, the description compensates by enumerating the returned fields (ruleId, engine, description, help, helpUrl, tags/wcag, fixability, fix), and all six parameters are optional and fully documented in the schema. Nothing an agent needs to select or invoke this tool is missing.

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 coverage is 100%, so the baseline is 3, but the description goes further by explaining what fixability values mean (mechanical | contextual | visual) and why one would filter on them, and by tying rule metadata to the filter. The 'context' and 'llm_model' analytics params are explained only in the schema, keeping it out of 5 territory.

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?

States a specific verb and resource ('List accessibility rules from both engines') plus the exact scope (axe-core 104 rules, WebAbility 90+) and the optional-filter behavior. No sibling tool lists rules — the others scan, check, or fix — so the agent can tell this is the catalog lookup rather than an execution tool.

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?

Gives a clear use context: filter by fixability 'so you can pick the rules worth auto-fixing before scanning,' which positions it as a pre-scan discovery step. It never states when NOT to use it or names an alternative tool, so it stops short of a 5.

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

All webability toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources