Skip to main content
Glama
Sign In
PhantomHand

PhantomHand

by SilenceEchoLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_type

Type text into the active browser element by injecting physical keystrokes. Click the target element first, then send the text input.

Instructions

Inject physical keystrokes into the active element (Requires clicking the element first).

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": {
      "text": "<text>"
    },
    "name": "browser_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It reveals that clicking is required but fails to mention side effects like triggering key events, speed, or whether it clears existing content. Does not address potential issues with non-interactive elements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, but it sacrifices critical information. It is a single sentence that could be expanded without losing conciseness.

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

Completeness2/5

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

Given the lack of output schema, 0% parameter coverage, and numerous sibling tools, the description is insufficient. It does not explain return values, error conditions (e.g., element not focusable), or how it differs from other typing-related tools.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only says 'inject physical keystrokes' without explaining the single parameter 'text' beyond its obvious meaning. No detail on supported characters, special keys, or handling of empty strings.

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?

The description clearly states it injects keystrokes into the active element, which is a specific verb and resource. It distinguishes from sibling tools like browser_keyboard_shortcut or browser_press_key. However, 'active element' could be more precise (e.g., focused input field).

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?

Only mentions the prerequisite of clicking the element first. Does not provide when to use this tool versus alternatives like browser_set_value, browser_clipboard_set, or browser_press_key. No when-not guidance.

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