Skip to main content
Glama

Get a WCAG manual checklist

check_wcag_checklist
Read-only

Returns the WCAG criteria that apply to a UI component, with the manual check a human must run and component-specific accessibility notes.

Instructions

Return the WCAG criteria that apply to a component, each with the manual check a human must run and the component-specific accessibility notes.

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": {
      "id": "<id>"
    },
    "name": "check_wcag_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesComponent id.
levelNoReturn all criteria or only AAA ones.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare this is a safe, closed-world read (readOnlyHint=true, openWorldHint=false), so the description's main added value is describing the shape of the result: each criterion paired with a manual check and component-specific notes. It says nothing about behavior for an unknown component id, result size, or grouping, leaving meaningful gaps beyond the annotation coverage.

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?

A single front-loaded sentence with no filler; the key output content (manual check, component-specific notes) is stated immediately rather than buried.

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?

For a simple two-parameter read tool with no output schema and full schema coverage, the description is nearly sufficient: it explains what is returned and why it is human-oriented. The only shortfall is the absence of guidance on id sourcing and the level filter.

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%, including the 'level' enum ('all' vs 'aaa'), so the schema does the heavy lifting. The description only implicitly ties 'component' to the id parameter and never mentions the level filter at all, adding little beyond the structured fields.

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 names a specific verb and resource ('Return the WCAG criteria that apply to a component') and even characterizes the payload (manual check per criterion plus component-specific notes). It is clear what the tool does, but it never contrasts itself with siblings like get_component or get_ai_prompt, so an agent must infer the boundary.

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: 'criteria that apply to a component' suggests calling it when you need accessibility checks for a known component. There is no explicit when-to-use or when-not-to-use statement, and no mention of prerequisites (e.g., needing an id from list_components first).

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