Skip to main content
Glama
Sign In
chrome-fast

chrome-fast

by ventos312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

type

Enters text into input, textarea, or contenteditable elements by focusing the field, inserting text, and optionally clearing or submitting with Enter.

Instructions

Type text into an input, textarea or contenteditable element: focuses it, then inserts the text as if typed. Returns the updated page content.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to type
clearNoReplace the existing content instead of appending to it (default: false)
selectorYesElement to type into: a ref number from get_page/navigate (e.g. "3") or a CSS selector
pressEnterNoPress Enter after typing, e.g. to submit a form or send a message (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/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 disclosure burden, and it does add real value: it reveals the focus step, the simulated-typing behavior, and the return value. It does not disclose side effects beyond typing (e.g. that pressEnter can submit a form), behavior when the selector matches nothing, or whether existing content is preserved by default.

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?

Two short sentences, front-loaded with the action and supported targets, followed by side effect and return value. No redundant or filler wording; only slight tightening would earn a 5.

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?

The tool is simple, all four parameters are schema-documented, and no output schema exists while the description states what comes back. However, with zero annotations the description should say more about mutation safety and failure modes, and it omits when this is preferable to fill_form.

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 description coverage is 100%, so clear, pressEnter and selector are already fully documented in structured form. The description adds only that typing targets input/textarea/contenteditable elements, which is a modest semantic gain over the schema.

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 gives a specific verb and resource ("Type text into an input, textarea or contenteditable element") and enumerates the supported element types, which lets an agent distinguish this from click or evaluate. It stops short of naming the closest sibling (fill_form), so differentiation is inferred from scope rather than stated.

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 only implied by the element-type scope: it is for typing into one located element. There is no explicit statement of when to prefer this over fill_form (for multiple fields at once) or evaluate, and no prerequisites such as the element needing to already exist on the page.

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