Skip to main content
Glama
yfe404

proxy-mcp

by yfe404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

humanizer_type

Type text into the focused browser element using keyboard simulation, enabling automated input and form filling within intercepted pages.

Instructions

Type text into the focused element via page.keyboard.type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to type
delay_msNoOptional Playwright delay per character in ms.
target_idYesTarget ID from interceptor_browser_launch

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.3
    • changedInput schema / properties / target_id / description
      Previous value: -"Target ID from interceptor_browser_launch or interceptor_camoufox_launch"New value: +"Target ID from interceptor_browser_launch"
  2. Changed2 schema fields changedv3.3.2
    • changedInput schema / properties / delay_ms / description
      Previous value: -"Extra delay per character in ms. Omit to let cloakbrowser pick its own humanized cadence."New value: +"Optional Playwright delay per character in ms."
    • changedInput schema / properties / target_id / description
      Previous value: -"Browser target ID from interceptor_browser_launch"New value: +"Target ID from interceptor_browser_launch or interceptor_camoufox_launch"
  3. Changed4 schema fields changedv2.3.0
    • addedInput schema / properties / delay_ms
      Added value: +{
+  "description": "Extra delay per character in ms. Omit to let cloakbrowser pick its own humanized cadence.",
+  "type": "number"
+}
    • removedInput schema / properties / error_rate
      Removed value: -{
-  "default": 0,
-  "description": "Typo probability per character, 0-1 (default: 0)",
-  "type": "number"
-}
    • changedInput schema / properties / target_id / description
      Previous value: -"Chrome target ID from interceptor_chrome_launch"New value: +"Browser target ID from interceptor_browser_launch"
    • removedInput schema / properties / wpm
      Removed value: -{
-  "default": 40,
-  "description": "Typing speed in words per minute (default: 40)",
-  "type": "number"
-}
  4. Addedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

The description adds a useful behavioral detail: typing targets whatever element currently has focus and uses keyboard events via page.keyboard.type. Since no annotations are provided, this helps, but it does not state what happens when nothing is focused, whether existing text is replaced or appended, or what side effects typing may cause.

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?

A single sentence that front-loads the action and no filler. It is minimal but every word contributes to the core behavior.

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 and the schema covers all parameters, so the basic call contract is visible. However, with no output schema and no annotations, the description omits return/error behavior and failure conditions such as missing focus or inactive browser.

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 text, delay_ms, and target_id are already documented in the schema. The description adds only the 'focused element' context and no further parameter-level semantics.

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 concrete action ('type') and a resource ('focused element') plus the Playwright mechanism ('page.keyboard.type'). The verb distinguishes it from sibling humanizer_click/scroll/idle, though it doesn't explicitly name an alternative tool.

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?

No guidance on when to choose this tool over humanizer_click/evaluate or how to prepare the element to receive focus. Use is only implied by the tool name and sibling set, not explicitly described.

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