Skip to main content
Glama
Sign In
Scout

Scout

by Lautrek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_press_key

Simulate pressing a keyboard key (e.g., Enter, Escape) in the browser to trigger page interactions.

Instructions

Press a keyboard key (e.g. Enter, Escape, ArrowDown, Backspace).

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": {
      "key": "<key>"
    },
    "name": "scout_press_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesKey name from Playwright (Enter, Escape, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose side effects (e.g., whether it simulates keydown/keyup, if it requires element focus, or what happens if the key is invalid). Minimal behavioral context.

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?

Single sentence with no fluff. All content is essential and front-loaded.

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 simple 1-param tool, the description is sufficient but could be improved by mentioning that the key is pressed on the currently focused element or page, and optionally listing common use cases. As-is, it leaves questions unanswered but is not critically incomplete.

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% with a clear description. The tool description adds a few more examples (ArrowDown, Backspace) but does not significantly enhance meaning beyond the schema. Baseline 3 is appropriate.

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?

The description states 'Press a keyboard key' with examples (Enter, Escape, ArrowDown, Backspace). The verb-and-resource construction is specific, and it clearly distinguishes from siblings like scout_type (types text) and scout_click (clicks mouse).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., scout_type for typing, scout_click for clicking). It does not specify if the key is pressed on the current page or a focused element, or list any prerequisites.

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