Skip to main content
Glama
Sign In
Scout

Scout

by Lautrek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_evaluate

Execute JavaScript in the current page to read its state, interact with elements blocked by shadow DOM overlays, or perform any DOM operation not covered by other tools.

Instructions

Execute JavaScript in the current page and return the result. Use for: reading page state, clicking elements blocked by shadow DOM overlays, interacting with Web Components, or any DOM operation not covered by other tools. The code runs in the page context with full DOM access. Returns the serialized result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "scout_evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesJavaScript code to execute in the page. Must be a valid expression or IIFE. The return value is serialized to JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Says code runs with full DOM access and returns serialized result, but does not disclose potential destructive side effects or error handling, leaving some behavioral ambiguity.

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?

Two sentences with a bullet-point list, front-loaded with the main action. Every sentence is informative and non-redundant.

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?

Covers purpose, use cases, and behavior. No output schema, but mentions serialized return. Could mention error handling or async limitations for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds value by specifying 'valid expression or IIFE' and noting JSON serialization, providing more guidance than the schema alone.

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?

Clearly states it executes JavaScript and returns the result. Lists specific use cases like reading page state and interacting with shadow DOM, distinguishing from siblings like scout_click or scout_type.

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 says 'Use for:' and enumerates scenarios. Implies when not to use by mentioning 'any DOM operation not covered by other tools', but lacks explicit exclusion examples.

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