Skip to main content
Glama
accessibility-mcp-demo

accessibility-mcp-demo

by KWADMOD

List scan targets

list_scan_targets
Read-onlyIdempotent

Lists the scan backends available for scanning a web page, so users can see which accessibility checkers they can choose. Call only when asking what scanners are available.

Instructions

List the scan backends available to scan_page. You rarely need this: scan_page uses the built-in 'local' checker by default. Call it only if the user asks what scanners are available.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context: that 'local' is the implicit default checker used by scan_page, which explains why the tool is seldom needed. It stops short of describing the shape or size of the returned list, but no output schema exists and the surface is trivially small.

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, zero filler, with the primary purpose front-loaded and the usage caveat immediately after. Every sentence carries distinct information: what it lists, why it is rarely needed, and the condition that justifies calling it.

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 zero-parameter read-only enumeration tool with annotations covering safety, nothing an agent needs in order to decide whether to call it is missing. The absence of return-value detail is acceptable given the trivial output and lack of an output schema.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the call is unconditional and requires no arguments.

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?

Names a specific verb and resource (list the scan backends) and ties the resource to the sibling that consumes it (scan_page), so an agent can immediately tell this is a discovery/enumeration tool rather than a scanning action.

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?

Explicitly states when not to use it ("You rarely need this: scan_page uses the built-in 'local' checker by default") and the exact trigger for calling it ("only if the user asks what scanners are available"). Both the default path and the exception are covered with no inference required.

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

Deploy Server

Other Tools