Skip to main content
Glama
brunoboto96

SceneScout

by brunoboto96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_crawl

Visits known or specified routes in one call, records coverage, and returns per-route health summaries that flag errors, dead-ends, auth redirects, and loading or alert-only views.

Instructions

Engine-side route sweep in ONE call: visits each path (default: all known routes not yet visited), records states into coverage memory, and returns a per-route health summary (HTTP status, element count, what the main area holds, oracle violations, dead-ends, auth-redirects, and ERROR-VIEW or STILL-LOADING for a main area showing only an alert or a loading placeholder). Navigation-only — safe in read-only mode. Use this FIRST for broad coverage; explore interactively only where it flags problems or where journeys matter.

Input Schema

NameRequiredDescriptionDefault
pathsNoPaths to visit, e.g. ['/orders','/settings'], or full URLs on the attached origin. A path resolves from the origin's root, whatever page the session attached on. Omit to crawl all unvisited known routes.
sessionNoTarget this session directly instead of the active one — pass it explicitly when dispatching to MULTIPLE sessions in one turn (e.g. two scout_click calls with different `session`), which then run CONCURRENTLY rather than queueing. Omit for single-session sequential use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.31.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv3.17.0
    • changedInput schema / properties / paths / description
      Previous value: -"Paths to visit, e.g. ['/orders','/settings']. Omit to crawl all unvisited known routes."New value: +"Paths to visit, e.g. ['/orders','/settings'], or full URLs on the attached origin. A path resolves from the origin's root, whatever page the session attached on. Omit to crawl all unvisited known routes."
  3. Addedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses the side effect (states recorded into coverage memory), the safety profile ('Navigation-only — safe in read-only mode'), and the default crawl scope (all known routes not yet visited). It does not disclose cost/duration, request volume, or what happens on the 150-path cap, which matters for a tool that sweeps up to 150 routes in one call.

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?

The lead clause front-loads the identity and the 'ONE call' differentiator, and the closing sentence carries the routing advice. The first sentence is dense with a long parenthetical status glossary, but each item listed is information an agent needs to interpret the return value.

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?

No output schema exists, and the description compensates by enumerating the returned per-route signals including the special ERROR-VIEW and STILL-LOADING states. Combined with the stated default scope and safety mode, an agent has enough to call it and interpret results without further discovery.

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 schema already explains path resolution semantics and the concurrent multi-session use of `session`, so the description adds little beyond restating that it visits 'each path'. Baseline 3 applies since structured fields do the heavy lifting.

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?

States a specific verb and resource ('route sweep... visits each path') plus the exact outputs: coverage memory writes and a per-route health summary enumerating HTTP status, element count, main-area contents, oracle violations, dead-ends and auth-redirects. It also carves out its scope against the interactive tools ('Navigation-only', 'explore interactively only where it flags problems'), so an agent can separate it from scout_click/scout_navigate 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?

'Use this FIRST for broad coverage; explore interactively only where it flags problems or where journeys matter' is an explicit ordering rule with a named condition that selects the alternative. The default behavior when `paths` is omitted is also stated, so the agent knows what happens on a bare call.

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