Skip to main content
Glama
Sign In

Fixlight

by io.github.fernwaylabs
OverviewDiscussionsAdmin

Scan a web page for accessibility problems

scan_url
Read-onlyIdempotent

Checks one public web page with automated accessibility tests (axe-core) and returns plain-English findings, worst first, each with why it matters and how to fix it. Notes which findings the free Fixlight WordPress plugin fixes on its own. Automated checks find many problems, but not all of them: a page with no findings here can still have barriers for some visitors, and this tool never scores or labels a site as a whole.

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": {
      "url": "<url>"
    },
    "name": "scan_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe public http(s) address of the page to check, for example https://example.com/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description explains the output format (plain-English findings, worst first, each with why it matters and how to fix it), notes WordPress plugin coverage, and discloses the significant limitation that automated checks find many but not all barriers. This adds substantial behavioral context not present in the readOnly/openWorld/idempotent annotations.

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?

The description is front-loaded with what the tool does and what it returns, then adds the key caveat about automated checking limits. Every sentence contributes useful information, and there is no redundant or vague wording.

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 one-parameter read-only scanning tool with no output schema, the description is complete: it covers purpose, return format, ordering, remediation guidance, plugin-fix notes, and the central limitation of automated accessibility testing. Nothing an agent needs in order to decide whether and how to call it is missing.

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 coverage is 100%, and the single URL parameter is already documented as a public http(s) address. The description reinforces that only one public web page is checked, but it does not add syntax or format details beyond what the schema provides, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Checks') and a clear resource ('one public web page') and names the underlying axe-core tests and return format. An agent can immediately understand that this is a single-page accessibility scan rather than a site-wide audit or score.

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 scope makes the intended use clear: checking one public page, not scoring or labeling a whole site. It also explicitly warns that clean results do not guarantee full accessibility. There are no sibling tools to compare against, but the guidance stops short of naming alternatives or detailed prerequisites.

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

All Fixlight toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources