Skip to main content
Glama

List Rules

list-rules
Read-onlyIdempotent

Lists checklist rules as records, filtered by component, ID, scope, layer, level or check. Each rule has a stable ID to cite in reviews and commits, its level (must or should), its scope, its requirement, how to check it (like a unit test, a review or axe's button-name rule) and a link to it.

WHEN TO USE: to review code rule by rule, to get only the rules that apply to a task, to look rules up by ID, or to find the ones a tool can check. Pass scope ["component", "both"] to build or review a component, and ["usage", "both"] to review a screen that uses it. WHEN NOT TO USE: for a component's API, DOM contract and tokens, use get-contract, which has every rule too.

It returns up to 50 rules at a time, and total counts every rule that matches. When there are more, pass nextOffset as offset, with the same filters, to get the next page.

A component meets the standard when it meets every must rule. Each should rule is expected unless there's a good reason not to follow it.

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-rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoThe IDs of the rules to look up, like ["button/keep-focus"].
checkNoHow the rule is checked.
layerNoui (how it looks), ux (user experience), dx (developer experience) or ax (agentic experience).
levelNo
limitNoHow many rules to return, at most.
scopeNoWho meets the rule: component (the component itself), usage (the code that uses it) or both. Rules without a scope, like the Design Tokens', match any scope.
offsetNoWhere the page starts: 0, or the nextOffset of the page before.
automatedNotrue for the rules tools check all of (unit tests, axe, a type check, a linter or a visual regression test), false for the ones a person checks, at least in part.
componentNoThe component or foundation, like button or design-tokens.

Output Schema

NameRequiredDescriptionDefault
rulesYes
totalYesHow many rules match, on every page.
unknownNoThe IDs asked for that no rule has, with the ones that might have been meant.
nextOffsetNoThe offset of the next page, when there is one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "field",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "select",
      -  "spinner",
      -  "switch",
      -  "tag-group",
      -  "tag",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "combobox",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "select",
      +  "spinner",
      +  "switch",
      +  "tag-group",
      +  "tag",
      +  "textarea",
      +  "tooltip"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "field",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "select",
      -  "spinner",
      -  "switch",
      -  "tag",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "select",
      +  "spinner",
      +  "switch",
      +  "tag-group",
      +  "tag",
      +  "textarea",
      +  "tooltip"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "field",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "select",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "select",
      +  "spinner",
      +  "switch",
      +  "tag",
      +  "textarea",
      +  "tooltip"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "field",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "select",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "input",
      -  "radio-group",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "radio-group",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "input",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "input",
      +  "radio-group",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "input",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "radio-group",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "input",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  9. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "card",
      -  "checkbox",
      -  "dialog",
      -  "switch",
      -  "textarea",
      -  "tooltip",
      -  "checkbox-group"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "input",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  10. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "card",
      -  "checkbox",
      -  "switch",
      -  "textarea",
      -  "tooltip",
      -  "checkbox-group"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "card",
      +  "checkbox",
      +  "dialog",
      +  "switch",
      +  "textarea",
      +  "tooltip",
      +  "checkbox-group"
      +]
  11. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "card",
      -  "checkbox",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "card",
      +  "checkbox",
      +  "switch",
      +  "textarea",
      +  "tooltip",
      +  "checkbox-group"
      +]
  12. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "card",
      -  "checkbox",
      -  "switch",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "card",
      +  "checkbox",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  13. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "switch",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "card",
      +  "checkbox",
      +  "switch",
      +  "tooltip"
      +]
  14. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "tooltip"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "switch",
      +  "tooltip"
      +]
  15. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input"
      -]New value: +[
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "tooltip"
      +]
  16. Changed4 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 50,
      +  "description": "How many rules to return, at most.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Where the page starts: 0, or the nextOffset of the page before.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / nextOffset
      Added value: +{
      +  "description": "The offset of the next page, when there is one.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / total / description
      Added value: +"How many rules match, on every page."
  17. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. Beyond that, the description adds meaningful behavior: it returns up to 50 rules at a time, reports a total count of matching rules, and explains how to paginate with nextOffset as offset using the same filters. It also explains the stable ID, level semantics, and that a component meets the standard when every must rule is met.

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?

The definition is front-loaded with what the tool does, then gives clear WHEN TO USE and WHEN NOT TO USE blocks. It is generally efficient, though some rule-field detail overlaps with what the output schema likely already provides.

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?

For a nine-parameter filtered list tool with an output schema, the description covers the essential context an agent needs: purpose, filter scope, when to use it, when to choose the sibling get-contract instead, and how pagination works. The compliance semantics for must and should rules are a useful addition rather than an omission.

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 description coverage is high at 89%, so the schema already carries most parameter documentation. The description adds useful interpretation for the scope filter by explaining that ["component", "both"] is for building or reviewing a component and ["usage", "both"] is for reviewing a screen that uses it, plus it reinforces pagination behavior around offset and page size.

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 states a specific verb and resource: it lists checklist rules as records with defined filters. It also distinguishes this tool from the sibling get-contract by explaining that get-contract covers a component's API, DOM contract and tokens, while this tool is for rule-by-rule review.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The WHEN TO USE section gives concrete scenarios: reviewing code rule by rule, getting only applicable rules, looking up rules by ID, and finding tool-checkable rules. The WHEN NOT TO USE section names get-contract as the alternative for component API/DOM/token needs, and the scope guidance further tells the agent which filter values to use for component versus screen reviews.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.