Skip to main content
Glama

List A11yKit components

list_components
Read-only

Lists 18 senior-first UI components with tier (free/Pro), WCAG criteria, and tags; filter by tier, tag, or keyword to choose accessible components.

Instructions

List the 18 senior-first components with tier (free/pro), WCAG criteria and tags. Filter by tier, tag or keyword. Free components include MIT source; Pro components list the spec only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly components carrying this tag, for example kiosk, care, form, speech.
tierNoRestrict to free or Pro components.all
limitNoMaximum number of rows to return.
queryNoCase-insensitive text match on id, name, tags and WCAG criteria.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description still adds genuinely useful behavioral context: free components come with MIT source while Pro components list the spec only, which materially affects what an agent gets back. It omits any mention of the 50-row cap or result ordering, which keeps it from a 5.

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?

Three short sentences, front-loaded with the resource and its count, then filtering, then the free-vs-Pro payload distinction. Nothing is redundant or padding.

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 sketches the row shape (tier, WCAG criteria, tags, MIT source vs spec). For a four-param read-only list tool this is close to complete; only pagination/limit behavior remains unstated.

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%, so all four parameters (tag, tier, limit, query) are already documented with examples and an enum. The description only restates the filter dimensions and adds no syntax or interaction detail beyond the schema, so baseline 3 applies.

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?

States a specific verb plus resource ("List the 18 senior-first components") and enumerates what each row carries: tier (free/pro), WCAG criteria and tags. The plural framing implicitly separates it from get_component, but no sibling is named explicitly, so differentiation is left to inference.

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?

"Filter by tier, tag or keyword" implies when the filters are useful but gives no explicit when-to-use, when-not-to-use, or direction to get_component for a single component's full detail. Guidance is present but thin.

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