Skip to main content
Glama

Elementum Design System MCP

lint_accessibility

Static HTML accessibility linter for common WCAG 2.2 labeling and attribute issues (not a substitute for real-browser axe-core auditing).

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": {
      "markup": "<markup>"
    },
    "name": "lint_accessibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
markupYesHTML markup snippet to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it usefully discloses the analysis is static and limited in coverage, which sets expectations about false negatives. It does not say what the tool returns (issue list, severity, line references) or whether it fetches resources, leaving meaningful gaps for an unannotated tool.

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 sentence that front-loads the core purpose and attaches the scope caveat compactly. Nothing is wasted or redundant.

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 one-parameter static analysis tool with no output schema, the description covers purpose and limits adequately. The main omission is any hint of the result shape an agent should expect when interpreting findings.

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?

Only one parameter exists and schema coverage is 100%, with the schema already describing it as an 'HTML markup snippet to inspect'. The description adds no further detail on format, size limits, or whether full documents are accepted, 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?

Names a specific verb and resource ('Static HTML accessibility linter') plus a concrete scope ('common WCAG 2.2 labeling and attribute issues'). The parenthetical distinguishes it from real-browser axe-core auditing, which implicitly separates it from a browser-based sibling, though no sibling is named.

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?

The parenthetical supplies a clear when-not ('not a substitute for real-browser axe-core auditing'), which tells the agent this is for static markup checks only. It stops short of naming the alternative tool to use for full auditing, so routing is inferred rather than explicit.

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.