Skip to main content
Glama

type

Fill a referenced form field with text via real key events, optionally submit, and return what changed on the page.

Instructions

Replace the content of a field (by ref) with text using real key events.

To choose from a dropdown, use select. Date, time, color and range inputs take
their value format instead: date YYYY-MM-DD, time HH:MM (24-hour), datetime-local
YYYY-MM-DDTHH:MM, month YYYY-MM, week YYYY-Www, color #rrggbb. Newlines in text are typed as
Shift+Enter, so they don't send chat messages; submit=true presses Enter after. Reports what
changed on the page, like click.

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

Input Schema

NameRequiredDescriptionDefault
refYes
textYes
submitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the key-event mechanism, that newlines become Shift+Enter so chat messages aren't sent, that submit=true presses Enter, and that it reports page changes 'like click'. It leaves out what happens if the ref is stale/hidden or whether existing content is replaced destructively beyond the word 'replace'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and the sibling routing are front-loaded in the first two sentences, with format details after. The long enumeration of input-type formats is dense but each entry earns its place as disambiguation.

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?

No output schema or annotations exist, yet the description covers mechanism, side effects, submission, return behavior in outline, and alternatives. The main remaining gap for a 3-parameter mutation tool is ref provenance and failure behavior.

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 0%, so the description must compensate. It adds real meaning for 'text' (newline handling, per-input-type formats) and 'submit' (presses Enter after), but 'ref' is only mentioned as an opaque identifier with no explanation of where a ref comes from or how it is obtained.

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, resource and mechanism: 'Replace the content of a field (by ref) with text using real key events.' It explicitly distinguishes itself from the sibling 'select' for dropdowns, so an agent can route correctly without opening the schemas.

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

Usage Guidelines5/5

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

Names the alternative tool and the condition that selects it ('To choose from a dropdown, use select'), then adds per-input-type value formats to prevent misuse on date/time/color/range fields. It also explains the submit=true path for submitting after typing.

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