Skip to main content
Glama
snayyar00

@webability/mcp

by snayyar00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Scan a multi-page user flow

flow_scan
Read-onlyIdempotent

Scan a multi-page user journey. Walks startUrl plus the autoNavigate URLs sequentially (deterministic — one page fully rendered and scanned before the next), then returns ONE consolidated report with issues deduplicated across pages…

Instructions

Scan a multi-page user journey. Walks startUrl plus the autoNavigate URLs sequentially (deterministic — one page fully rendered and scanned before the next), then returns ONE consolidated report with issues deduplicated across pages, each carrying the same fix payload as scan_page. Every requested URL gets an explicit outcome in pages[] (scanned / nav_failed / scan_failed / redirected_duplicate / duplicate_request / skipped_cap / blocked — bot-challenge, not a clean page) — a page is never silently dropped. Better than per-page scans for journeys (login → checkout etc). Without autoNavigate it scans only startUrl, exactly like scan_page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wcagNoOnly these WCAG criteria. A prefix selects the whole guideline ("1.4") or principle ("2").
levelNoHighest WCAG conformance level to report. Default "AA" — Level AAA criteria are not reported. Pass "AAA" to include them (naming one AAA criterion in `wcag`, e.g. "3.2.5", also includes it).
rulesNoOnly these rule ids (WebAbility type such as "missing_alt" or axe rule id such as "image-alt"). See get_rules.
formatNo"compact" prints one line per element with rule metadata once. "json" returns every field (html, fix values, source). Default: JSON when it fits inline (under ~24k chars), otherwise compact plus a JSON summary of every count.
maxPagesNoMax pages to scan (default 10)
startUrlYesStarting URL of the journey
minImpactNoOnly findings at this severity or above (critical > serious > moderate > minor)
sourceRootNoLocal project root (local installs only) for `sourceCandidates[]` on issues without a framework `source` pointer.
autoNavigateNoThe URLs to walk after startUrl, in order (the MCP server is headless and cannot discover a journey interactively). Omit or pass [] to scan only startUrl as a single page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.0
    • changedInput schema / properties / autoNavigate / description
      Previous value: -"REQUIRED — the URLs to walk after startUrl (the MCP server is headless and cannot discover a journey interactively). For a single page, use scan_page instead."New value: +"The URLs to walk after startUrl, in order (the MCP server is headless and cannot discover a journey interactively). Omit or pass [] to scan only startUrl as a single page."
    • changedInput schema / required
      Previous value: -[
-  "startUrl",
-  "autoNavigate"
-]New value: +[
+  "startUrl"
+]
  2. Changed1 schema field changedv1.8.0
    • addedInput schema / properties / level
      Added value: +{
+  "description": "Highest WCAG conformance level to report. Default \"AA\" — Level AAA criteria are not reported. Pass \"AAA\" to include them (naming one AAA criterion in `wcag`, e.g. \"3.2.5\", also includes it).",
+  "enum": [
+    "A",
+    "AA",
+    "AAA"
+  ],
+  "type": "string"
+}
  3. Changed5 schema fields changedv1.7.0
    • addedInput schema / properties / format
      Added value: +{
+  "description": "\"compact\" prints one line per element with rule metadata once. \"json\" returns every field (html, fix values, source). Default: JSON when it fits inline (under ~24k chars), otherwise compact plus a JSON summary of every count.",
+  "enum": [
+    "json",
+    "compact"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / minImpact
      Added value: +{
+  "description": "Only findings at this severity or above (critical > serious > moderate > minor)",
+  "enum": [
+    "critical",
+    "serious",
+    "moderate",
+    "minor"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / rules
      Added value: +{
+  "description": "Only these rule ids (WebAbility type such as \"missing_alt\" or axe rule id such as \"image-alt\"). See get_rules.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / sourceRoot
      Added value: +{
+  "description": "Local project root (local installs only) for `sourceCandidates[]` on issues without a framework `source` pointer.",
+  "type": "string"
+}
    • addedInput schema / properties / wcag
      Added value: +{
+  "description": "Only these WCAG criteria. A prefix selects the whole guideline (\"1.4\") or principle (\"2\").",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  4. First observedv1.3.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description adds execution semantics annotations cannot express: deterministic page-by-page rendering, cross-page deduplication, a fixed set of per-URL outcome states (nav_failed, scan_failed, redirected_duplicate, duplicate_request, skipped_cap, blocked bot-challenge), and the guarantee that no page is silently dropped.

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?

Front-loaded and dense — the walk mechanism and the consolidated-report outcome come first, with the scan_page comparison at the end. It is one long paragraph with a heavy parenthetical enumerating status codes, which is informative but slightly unwieldy.

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?

There is no output schema, so the description must carry the return-shape burden, and it does: it names the consolidated report, deduplication, the fix payload parity with scan_page, and the pages[] outcome vocabulary. For a 9-parameter tool this leaves nothing an agent needs to invoke it correctly unstated.

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 100%, so the baseline is 3. The description adds value beyond the schema by tying parameters together: autoNavigate's ordering role, the fact that omitting it collapses the call to a single-page scan, and the presence of a page cap implied by skipped_cap. It stops short of explaining maxPages truncation or sourceRoot behavior in prose.

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 gives a specific verb+resource ('Scan a multi-page user journey') and immediately defines the mechanism (walk startUrl plus autoNavigate URLs sequentially) plus the output (ONE consolidated, deduplicated report). It explicitly contrasts itself with scan_page, so an agent can distinguish it from the closest sibling without opening a schema.

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?

It states when to prefer this over alternatives ('Better than per-page scans for journeys (login → checkout etc)') and names the exact condition under which it degenerates to the sibling's behavior ('Without autoNavigate it scans only startUrl, exactly like scan_page'). Both the use case and the degenerate case are explicit.

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