Skip to main content
Glama

form_input

Set a form control's value by ref: enter text in fields, toggle checkboxes or radios, and pick select options by value or label for reliable browser form filling.

Instructions

Set the value of a form control by ref: text fields (replaces the value), checkboxes/radios (true/false), and selects (option value or visible label).

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": {
      "tabId": "<tabId>",
      "ref": "<ref>",
      "value": "<value>"
    },
    "name": "form_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
tabIdYesTab ID, from tabs_list or tab_create
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose meaningful per-type value semantics (text replaces existing content, booleans for checkboxes/radios, option value or visible label for selects). It omits whether input/change events fire, what happens on an invalid or stale ref, and whether a submit step is required afterward — all important for a mutation tool.

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?

It is a single sentence, front-loaded with the core action, with the control-type breakdown in a compact parenthetical. Dense but every clause carries information; no filler wording.

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 three-parameter mutation tool with no annotations and no output schema, the definition covers what to pass for each control type but not how to obtain a ref, what state changes on the page, or how failures surface. Adequate minimum, with clear gaps an agent would hit in practice.

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 only 33% (tabId is documented, ref and value are not), so the description must compensate. It does add real meaning for 'value' by mapping accepted types to control kinds, which the bare union type in the schema does not convey, but 'ref' is left entirely unexplained with no hint of where it comes from.

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 names a specific verb and resource ('Set the value of a form control by ref') and breaks the operation down by control type (text, checkbox/radio, select), so an agent knows exactly what the tool mutates. It does not, however, distinguish itself from siblings like 'type' or 'click', which can also affect form controls, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is implied by the control-type enumeration — pick this for checkboxes, radios and selects where 'type' would not work. But there is no explicit when-to-use statement, no guidance on preferring 'type' for text entry to trigger keystroke events, and no prerequisites such as obtaining a ref from read_page or find.

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