Skip to main content
Glama
brunoboto96

SceneScout

by brunoboto96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_capture

Save a PNG of one page element, including its bounds and margin, from a real screenshot to show someone how it looks.

Instructions

Save a PNG of ONE element — its bounds plus a margin, from a real screenshot — under .scenescout/captures/, to show a person how it looks. Give the element's ref from the latest scout_snapshot. Not a way to judge design: scout_design_audit measures it.

Input Schema

NameRequiredDescriptionDefault
keyNoInstead of a ref: the element's key from an earlier scout_capture result, to capture the same element on another deployment
refNoThe element's ref from the latest scout_snapshot
nameNoThe file's name: letters, digits and dashes. Default: capture
marginNoCSS pixels kept around the element. Default 8
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. Addedv3.14.1

TDQS

A3.9/5.0
Behavior3/5

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

Without annotations, the description carries the full burden. It discloses that it saves a file under a specific path and uses a real screenshot, which is useful, but it does not describe what the return value is, whether files are overwritten, or any permission/error behavior expected for a write tool.

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, front-loaded with the core action and output location. The prerequisite and exclusion follow logically with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with no annotations and no output schema, the description covers purpose, prerequisite, and one alternative adequately. However, it omits behavioral details an agent might need—such as the format of the return value or file collision behavior—leaving it minimally sufficient rather than complete.

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 the schema already documents each parameter thoroughly. The description adds a note about using a ref from the latest scout_snapshot, but that is already present in the schema's ref description, so it adds little semantic value beyond the structured fields.

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 (Save), resource (PNG of ONE element), scope (bounds plus margin), output location (.scenescout/captures/), and purpose (to show a person how it looks). It also explicitly distinguishes itself from the design-audit sibling, so an agent can tell what this tool uniquely does.

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?

Provides clear context: it requires a ref from the latest scout_snapshot and explicitly says it is not for judging design (use scout_design_audit instead). It does not mention the full-page screenshot sibling, but the 'ONE element' emphasis gives adequate guidance for most calls.

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