Skip to main content
Glama

scout_snapshot

Capture the current page state—URL, summary, interactable elements with stable refs, alerts, geometry, coverage, and oracle violations—and return a diff on re-snapshot to track changes.

Instructions

Capture the current page state: URL, state fingerprint, a one-line summary of the main area's heading and text, interactable elements with refs (e1, e2, …) and their state (pressed, selected, checked, expanded, current), what the page announces (alert and status regions, by their text), geometry issues, coverage, and oracle violations since the last action. Re-snapshotting a route returns a DIFF against its last snapshot, even after visiting elsewhere, and another tab of the same screen diffs against that screen's last tab; refs stay stable, including across a search or filter that rewrites only the query string. On a dense page, says what past the element cap was cut. Cheap — prefer this over screenshots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoForce a full element list instead of a diff
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. Addedv1.1.0

TDQS

A4.4/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so richly: it discloses the diff semantics (re-snapshot returns a DIFF even after visiting elsewhere, per-tab diffing), ref stability across query-string rewrites, truncation behavior past the element cap, and relative cost. These are non-obvious behaviors an agent could not infer from the name or schema.

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 with the core purpose, and every clause carries information (return fields, diff behavior, ref stability, cost). It is dense and somewhat run-on in the middle, which slightly hurts scannability, but there is little wasted text.

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 describe the return payload — and it does, itemizing exactly what a snapshot contains (refs, states, announcements, geometry, coverage, oracle violations) plus diff/truncation behavior. An agent has everything needed to call and interpret it.

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 description coverage is 100%, so both `full` and `session` are already documented in the schema, including the concurrency caveat. The description adds no format/semantic detail beyond that, so the baseline of 3 is correct when the schema does 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?

Specific verb ("Capture") plus a fully enumerated resource: URL, fingerprint, summary, interactable elements with refs, announcements, geometry, coverage, oracle violations. It explicitly positions itself against a sibling ("prefer this over screenshots"), so an agent can distinguish it from scout_screenshot/scout_capture 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear usage context: it names the alternative (screenshots) and states the cost tradeoff, and it explains the multi-session concurrency case for the `session` param. It lacks explicit when-not guidance against the many other scout_* capture/verify siblings, but the routing signal is strong.

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