Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

拟人输入

browser_type

Types text into a specified text input field, one character at a time. Use only for text boxes; dropdowns, options, and buttons fail and require click or select instead.

Instructions

通用:只对文本框逐字输入。下拉框、选项、按钮会直接失败,并说明该用点选还是点击。

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

Input Schema

NameRequiredDescriptionDefault
refYes输入框编号,例如 e2
textYes要输入的文字
clearNo输入前先全选并删除已有内容
submitNo输入完成后按 Enter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

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 the human-like character-by-character typing mode and the failure behavior on non-text elements, but says nothing about focus requirements, visibility/scrolling, or what a successful call 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?

Two short sentences with zero waste; the scope constraint is front-loaded and the failure-mode caveat follows immediately. Nothing is redundant or padded.

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 four-parameter mutation tool with no annotations and no output schema, the description covers purpose and failure modes but leaves the clear/submit semantics and success behavior entirely to the schema. Adequate but with visible gaps.

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 all four parameters (ref, text, clear, submit) are already documented in the schema. The description adds no meaning about the clear or submit flags, so the baseline of 3 applies.

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 states a specific verb and resource ('逐字输入' into '文本框') and explicitly scopes the tool to text inputs only. It distinguishes itself from click/select-style siblings by declaring that dropdowns, options, and buttons will fail, though it never names those siblings directly.

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

Usage Guidelines4/5

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

It gives clear when-not-to-use guidance: dropdowns, option lists, and buttons are out of scope, and the tool will report whether to use a select or a click instead. It stops short of naming the concrete alternative tools (e.g. browser_click), so the agent must infer the mapping.

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