SoftGlaze Browser MCP

Overview Schema Source Related Servers Discussions Admin

Type text

page_type

Types text into a page field one key at a time with human-like pauses, optionally clicks and clears a chosen field, and can press Enter to submit.

Instructions

Types text one key at a time with human-like gaps (SoftGlaze's human typer). With a selector it first clicks that field (clear: true empties it first); without, it types where the focus is. pressEnter submits afterwards. Up to 300 characters per call. Never type credentials the user did not give you for this exact site. Asks once per profile.

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

Input Schema

Name	Required	Description	Default
`text`	Yes
`clear`	No
`selector`	No
`profileId`	Yes
`pressEnter`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing typing cadence, focus-dependent targeting, the 300-character per-call limit, that clear:true wipes existing field content, and that a permission prompt appears once per profile. These are exactly the operational facts an agent cannot get from structured fields. The field-clearing behavior is not a contradiction of destructiveHint=false, since it is scoped to the target field and explicitly disclosed.

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?

Purpose is front-loaded in the opening clause, then modes, then the limit, then the safety rule. Every sentence carries a distinct fact with no filler, and parenthetical annotations for clear:true are compact rather than verbose.

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

Completeness4/5

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

For a 5-parameter mutation-style tool with zero schema description coverage and no output schema, the description supplies nearly everything needed: targeting modes, submission behavior, length cap, and a safety constraint. The only gap is profileId semantics and any indication of what is returned on success or failure.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and it largely does: selector (targets and focuses a field), clear (empties the field first), pressEnter (submits), text (limited to 300 characters). Only profileId is left unexplained, presumably a standard identifier shared across the toolset.

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?

States a specific verb and resource ('Types text one key at a time with human-like gaps') and immediately distinguishes itself from page_press_key and page_click by describing per-character typing versus single keystroke or click behavior.

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?

Explains the two usage modes clearly: with a selector it clicks the field first, without one it types at current focus, and pressEnter submits afterwards. It also sets a policy boundary ('Never type credentials the user did not give you for this exact site'). It does not explicitly route the agent to page_press_key for special keys or page_click for non-input targets, so the alternative-routing is implied rather than stated.

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