Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_patternA

Get the accessible implementation pattern for a UI component.

Args:
    component: The component name (e.g., "modal", "tabs", "combobox",
               "carousel", "menu", "dialog", "tooltip", "alert",
               "switch", "listbox", "treeview", "slider", "feed",
               "grid", "disclosure", "landmarks", "headings", "buttons",
               "link", "spinbutton", "meter", "menu button").

Returns:
    Detailed WAI-ARIA Authoring Practices pattern with code examples,
    keyboard interaction requirements, and ARIA roles/states/properties.
review_codeA

Review code for accessibility issues and suggest fixes.

Args:
    code: The HTML, JSX, TSX, Vue, or Svelte component code to review.
    component_type: Optional hint about what the component is
                    (e.g., "modal", "dropdown", "form").

Returns:
    Accessibility issues found with specific fix suggestions and
    references to WAI-ARIA patterns.
list_patternsA

List all available accessible component patterns.

Returns:
    A list of all component patterns available in the knowledge base.
check_contrastA

Check if two colors meet WCAG contrast ratio requirements.

Args:
    foreground: Foreground color as hex (e.g., "#333333" or "333").
    background: Background color as hex (e.g., "#ffffff" or "fff").

Returns:
    Contrast ratio and pass/fail for WCAG AA and AAA levels.

Prompts

Interactive templates invoked by user choice

NameDescription
audit-componentStep-by-step accessibility audit for a UI component. Provide the code and optionally the component type.
make-accessibleTransform inaccessible code into a fully accessible implementation. Provide the code and what the component is.
check-form-accessibilityAudit a form for accessibility — labels, errors, validation, and keyboard flow.
wcag-checklistGenerate a WCAG 2.2 compliance checklist for a page or component. Specify the conformance level.
aria-guideGet a complete ARIA implementation guide for a specific component type.

Resources

Contextual data attached and managed by the client

NameDescription
pattern-indexIndex of all WAI-ARIA component patterns in the knowledge base.

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: color contrast checking, retrieving patterns, listing patterns, and reviewing code. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (check_contrast, get_pattern, list_patterns, review_code), making the API predictable.

Tool Count5/5

With 4 tools, the server is well-scoped for its niche. It covers the core needs of an accessibility expert without being too sparse or bloated.

Completeness4/5

The server covers contrast checking, pattern reference, and code review. It lacks a dedicated tool for keyboard navigation testing or automated audit, but review_code can handle many issues.

Maintenance

ActivityInactive
ResponsivenessNo issues