Skip to main content
Glama
brunoboto96

SceneScout

by brunoboto96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_session

Lists live browser sessions or sets the default session used when tool calls omit a session, helping sequential workflows avoid repeating session IDs and check what is live.

Instructions

List live sessions, or set which one is the DEFAULT (used by any tool call that omits session). Prefer passing session directly on each tool call for multi-role work — that's what lets concurrent dispatch happen; scout_session is for sequential convenience (skip repeating session on every call) and for checking what's live. Both browsers stay live and authenticated regardless of which is default — re-snapshot a session after a break to see what changed while it was away.

Input Schema

NameRequiredDescriptionDefault
areaNoIn a guided check: the area this session is working on now, one of its plan's areas, shown to the person following the check. With `name`, that session (the default session is left as it is); without, the default one. Set it as each area starts.
nameNoSession to make the default; omit to list sessions
paceMsNoChange how fast this session acts, mid-run: a floor between actions in milliseconds, for when a person is watching and needs to keep up. 0 restores full speed. With `name`, applies to that session; without, to every live session — which is what 'slow everything down so I can follow' means.
sessionNoAlias for `name`.

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.25.0
    • addedInput schema / properties / area
      Added value: +{
+  "description": "In a guided check: the area this session is working on now, one of its plan's areas, shown to the person following the check. With `name`, that session (the default session is left as it is); without, the default one. Set it as each area starts.",
+  "enum": [
+    "sign-in",
+    "forms",
+    "broken-pages",
+    "phone",
+    "journey",
+    "tickets"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changedv3.4.0
    • addedInput schema / properties / paceMs
      Added value: +{
+  "description": "Change how fast this session acts, mid-run: a floor between actions in milliseconds, for when a person is watching and needs to keep up. 0 restores full speed. With `name`, applies to that session; without, to every live session — which is what 'slow everything down so I can follow' means.",
+  "maximum": 60000,
+  "minimum": 0,
+  "type": "integer"
+}
  4. Addedv1.1.0

TDQS

A3.8/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 delivers non-obvious behavioral facts: setting a default has no side effect on liveness or auth state, both browsers stay authenticated regardless of which is default, and a re-snapshot is needed to see what changed while a session was away. It does not say whether the default persists across calls/connections or what the listing returns.

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-loads the two primary behaviors in the first clause, then qualifies with the preferred alternative. Dense but mostly earning its words; the parenthetical asides and em-dash clauses make it slightly rambling relative to the core message.

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?

No output schema and no annotations, so the description must hold the whole story — and it leaves out the pacing and guided-area functions entirely, plus any indication of what a listing returns. What it does cover (default-session semantics, liveness guarantees) is complete and correct.

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 baseline is 3. The description adds genuine meaning for `name`/`session` by framing them as 'the session every unqualified call falls back to', which is more than the schema states. But `paceMs` and `area` are never mentioned in the description at all, so it contributes nothing for two of the four parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States two specific verbs (list live sessions, set the DEFAULT session) on a named resource, and explains that omitting `session` elsewhere routes through the default. It is clearly distinguishable from siblings like scout_status. However, it covers only two of the tool's four capabilities — nothing signals that this same tool also throttles action pace (`paceMs`) or marks the current guided area (`area`), so the stated purpose under-describes the tool's scope.

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?

Explicitly names the preferred alternative (pass `session` directly on each call for multi-role/concurrent work) and characterizes this tool's niche as sequential convenience plus introspection. That is real when/when-not guidance against a concrete alternative. It stops short of when to use the pace-throttling and area-tracking modes.

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