Skip to main content
Glama
Sign In
gecko-mcp

gecko-mcp

by Frumane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

type_text

Type text into any input or textarea by CSS selector. Clears the field before typing by default, with optional control over clearing and target tab.

Instructions

Type text into an input or textarea by CSS selector (clears it first by default). Targets the active tab unless a browserId is given.

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_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS selector of the input/textarea.
textYesThe text to type.
clearNoClear the field before typing. Default: true.
browserIdNoTarget tab (from list_tabs). Defaults to active.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.4

TDQS

B3.3/5.0
Behavior1/5

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

Description states 'clears it first by default', indicating a destructive action (modifying the field content), but the annotation destructiveHint is false. This contradiction is a serious flaw. Additionally, beyond the contradiction, the description adds some behavioral context but the contradiction outweighs it.

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 clear, front-loaded sentences with no extraneous information. Every word contributes to understanding the tool's purpose and key behaviors.

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?

Description covers essential behaviors (clearing, tab targeting) but lacks information on error handling (invalid selector), special characters, and distinctions from sibling tools like 'real_type' (keyboard vs DOM input). Given the absence of an output schema, more contextual depth would aid agent decision-making.

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%, providing descriptions for all 4 parameters. The description adds relevant context about clearing default and browserId targeting, but does not significantly enhance understanding beyond schema descriptions. Baseline score of 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?

Description clearly states the action (type text), the resource (input/textarea via CSS selector), and key behavior (clears first by default). It also specifies scope (active tab unless browserId given), which distinguishes it from similar tools like 'real_type' or 'press_key'.

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?

The description mentions targeting active tab unless browserId is given, providing some context for when to use the browserId parameter. However, it lacks explicit guidance on when to prefer this tool over alternatives like 'real_type' or 'fill_form', and does not state any prerequisites or exclusions.

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