Skip to main content
Glama
Sign In
HomarUScc

HomarUScc

by kcdjmaxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_type

Enter text into webpage input fields using a CSS selector. Automates form filling for browser automation.

Instructions

Type text into an input element by CSS selector.

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": "browser_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type
selectorYesCSS selector of input element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic action without addressing nuances like whether it focuses the element first, clears existing text, or waits for the element to be ready, which are critical for browser automation tools.

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?

The description is a single sentence with no filler, making it highly concise and efficiently structured.

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, but the description omits any behavioral context such as preconditions (e.g., page must be loaded) or effects (e.g., does it clear the field first). There is no output schema, so return behavior is also unclear, making it minimally adequate.

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%, so both parameters are already well-documented. The description reinforces the selector parameter but does not add significant new meaning beyond the schema.

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?

The description uses a specific verb ('Type'), identifies the resource ('input element'), and specifies the method ('by CSS selector'), making it clear and distinct from sibling tools like browser_click and browser_navigate.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for typing text, but there is no mention of when not to use it or references to sibling functions like browser_click or browser_evaluate.

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