Skip to main content
Glama
brunoboto96

SceneScout

by brunoboto96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_type

Types text into a text input, textarea, or composer by element ref, appending to existing content by default or clearing first with replace=true to correct or test boundary values.

Instructions

Type into a text input/textarea/composer by ref, the way a real user does: if the field already holds content (e.g. an @-mention chip a menu click inserted), the text is APPENDED at the end — preserving that content — and the result reports what was already there (a separating space is added only at a word-to-word boundary). Pass replace=true to clear the field first (correcting a previous entry); an empty textValue always clears. Appending fires input events but not keydown, so keydown-driven triggers (slash/mention menus) will not react to appended text. Use for both valid values and boundary/fuzz values (empty, very long, unicode, script tags). A value typed into a secret field (a password, a one-time code, a card number, a field labelled secret or token) is masked in the result and the log, as is what the field held.

Input Schema

NameRequiredDescriptionDefault
refYesElement ref, e.g. e12
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.
valueNoAlias for `textValue`.
replaceNoClear the field before typing instead of appending to existing content
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`.
textValueNoText to type
pressEnterNoPress Enter after typing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.31.0
    • removedInput schema / additionalProperties
      Removed value: -false
  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

A4.3/5.0
Behavior5/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 so: it discloses append-vs-clear semantics, that appending fires input events but not keydown, that the result reports prior content, the word-boundary space rule, and that secret-field values and prior contents are masked in both result and log. Those are non-obvious side effects an agent could not get from the 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?

Every sentence carries real information and the default (append) behavior is front-loaded before the replace exception. It is a single dense paragraph, though, and the masking sentence runs long enough that splitting it would aid scanning.

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

Completeness4/5

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

There is no output schema, and the description does cover what the result reports (prior content, masking). It is nearly complete for an 8-parameter mutation tool with no annotations, but is silent on failure modes such as an unresolvable ref or an element that is not an editable field, and never states that refs come from a snapshot.

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%, so the baseline is 3. The description adds modest meaning for `replace` ('correcting a previous entry') and an implicit empty-value rule for textValue, but says nothing about `pressEnter`, `task`, `session`, or the `value`/`objective` aliases beyond what the schema already documents.

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 (type) and resource (text input/textarea/composer) plus the addressing mechanism (by ref), and frames it as 'the way a real user does' to distinguish it from scripted value-setting. An agent can separate this from scout_press, scout_select, and scout_click without opening any 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?

Gives concrete conditions: append by default to preserve existing content, pass replace=true to correct a prior entry, empty textValue clears, and 'use for both valid values and boundary/fuzz values'. It also warns that keydown-driven slash/mention menus will not react to appended text, which implicitly routes that case elsewhere, but it never names scout_press as the alternative, leaving the agent to infer it.

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