Skip to main content
Glama
brunoboto96

SceneScout

by brunoboto96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_navigate

Navigate to a path or full URL on the attached origin to load a page for exploratory UI testing.

Instructions

Navigate to a path on the attached origin (e.g. '/orders') or a full URL on it. A path resolves from the origin's root, whatever page the session attached on. Also supports 'back' via scout_back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNoWhat you are DOING right now, in a few words: the action, not the acceptance criteria. "Filtering the documents register by status", "Filling the deviation form with invalid dates", "Signing in as QA_Team" — NOT "§2.4 filtering narrows the set and the filter is reflected in the URL", which is what you are CHECKING, not what you are doing. Naming the item you are on is fine ("§2.4: filtering the documents register"); keep the rest to what a colleague would see over your shoulder. It stays set until you pass a different one, so a batch costs a few words, not one per call. Required on the tools that act unless a journey or an earlier call already set one.
leaveNoHow to answer if the page asks to confirm leaving (a beforeunload prompt over unsent input): true leaves and discards that input, false stays. Omitted, observe and read-only stay and other modes leave. The result says when the page asked.
targetYesAbsolute URL or path like /settings
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.
objectiveNoOld name for `task` (2.0). Prefer `task`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.17.0
    • addedInput schema / properties / leave
      Added value: +{
+  "description": "How to answer if the page asks to confirm leaving (a beforeunload prompt over unsent input): true leaves and discards that input, false stays. Omitted, observe and read-only stay and other modes leave. The result says when the page asked.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / objective
      Added value: +{
+  "description": "Old name for `task` (2.0). Prefer `task`.",
+  "maxLength": 120,
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "What you are DOING right now, in a few words: the action, not the acceptance criteria. \"Filtering the documents register by status\", \"Filling the deviation form with invalid dates\", \"Signing in as QA_Team\" — NOT \"§2.4 filtering narrows the set and the filter is reflected in the URL\", which is what you are CHECKING, not what you are doing. Naming the item you are on is fine (\"§2.4: filtering the documents register\"); keep the rest to what a colleague would see over your shoulder. It stays set until you pass a different one, so a batch costs a few words, not one per call. Required on the tools that act unless a journey or an earlier call already set one.",
+  "maxLength": 120,
+  "type": "string"
+}
  3. Addedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose one genuinely non-obvious behavioral trait: a path resolves from the origin's root regardless of which page the session attached on. Beyond that it says nothing about whether navigation waits for load, how failures/redirects are surfaced, or whether the session/target stays attached — significant gaps for a tool whose whole job is a state-changing page transition.

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?

Three short sentences, front-loaded with the primary target semantics before the path-resolution nuance. The trailing sentence about scout_back earns its place by routing the agent, though it reads slightly oddly as a feature of this tool rather than a redirect.

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 annotations and no output schema, so the description must cover the behavioral profile — it covers target/path resolution but omits load-waiting behavior, failure modes, and what the caller receives back. The remaining four parameters are fully documented in the schema, so the gap is behavioral rather than parametric.

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 baseline is 3. The description does add meaning for `target` by clarifying that a path is resolved relative to the origin root rather than the current page — more than the schema's terse 'Absolute URL or path like /settings' — but it says nothing about `task`, `leave`, or `session`, relying entirely on the schema.

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 a specific verb ('Navigate to') and resource ('a path on the attached origin or a full URL on it'), with a concrete example ('/orders'). It also routes the agent away from this tool for back-navigation ('Also supports \'back\' via scout_back'), which gives partial sibling differentiation, though it does not distinguish itself from scout_click/scout_attach in the same way.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this is the tool for moving to a new page, and the description explicitly names scout_back as the alternative for back-navigation. However, there is no guidance on when to navigate vs. when the session is already on the target, nor any mention of prerequisites such as needing an attached session.

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