Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_pressKey

Sends a key or key chord, such as Enter, Tab or Control+A, to the focused element in an active TestingBot browser session to simulate real keyboard input during tests.

Instructions

Press a key (or chord) on the active browser session. Uses W3C key names: 'Enter', 'Tab', 'Escape', 'Control+A', 'Meta+Shift+Z', etc. Sent to the currently-focused element.

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

Input Schema

NameRequiredDescriptionDefault
keyYesKey name or chord
sessionIdYesSession ID from tb_openBrowser

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/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 usefully discloses target semantics (events go to the currently-focused element, not a selector-specified one), but says nothing about what happens if no element is focused, whether the call errors on unknown key names, or what the tool returns.

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?

Three short sentences, no filler: the action first, then the key-format rule with concrete examples, then the targeting behavior. Every sentence carries information an agent needs before calling.

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?

For a simple two-parameter input tool with no output schema, the description covers action, key syntax, session source, and event target, which is most of what an agent needs. Gaps are minor: no error behavior and no statement of what the call returns.

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 the baseline is 3, but the description earns above baseline by documenting the key-string format: W3C key names plus modifier-chord syntax ('Control+A', 'Meta+Shift+Z'), which the schema only calls 'Key name or chord'. The sessionId link to tb_openBrowser is also reinforced.

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 and resource ('Press a key (or chord) on the active browser session') and scopes it to the focused element, so an agent can distinguish it from text-entry siblings like tb_type. It stops short of naming an alternative explicitly, which keeps it from a 5.

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 'active browser session' and 'currently-focused element' framing tells the agent the context required, and the chord examples hint at keyboard-shortcut use. There is no explicit when-to-use versus tb_type or when-not guidance (e.g., use tb_type for literal text input).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.