Skip to main content
Glama

fill_form

Populate multiple browser form fields in one call by supplying element refs with values, covering text inputs, checkboxes, radios, and selects.

Instructions

Fill several fields at once. Text fields take a string, checkboxes and radios take true or false, selects take the option label or value.

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": {
      "fields": "<fields>"
    },
    "name": "fill_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
fieldsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the value-type contract per field kind (string for text, true/false for checkboxes and radios, label or value for selects), which is genuine behavioral information. It omits what happens on partial failure, whether the form is submitted or a navigation is awaited, and whether stale refs cause errors.

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?

Two short sentences, front-loaded with the action and followed immediately by the type contract. No filler, no restatement of the name.

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 mutation tool with no annotations and no output schema, the definition covers the input contract but leaves the outcome side blank: no statement of return value, error behavior, or whether filling triggers submission or navigation. Adequate to invoke, thin for predicting results.

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 50%: tab and ref are documented in the schema, but the polymorphic value field is not, and the description compensates by explaining the accepted types per field kind. That is real added meaning, though it does not cover ordering, duplicate refs, or what happens when a value type mismatches the element.

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 specific verb and resource ("Fill several fields at once") and implies batch semantics, which distinguishes it from single-element tools like click or press_key. It never says explicitly that it operates on browser page form elements, so the resource is inferred from context rather than stated.

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 when-to-use guidance: nothing says to prefer this over repeated click/press_key calls, nothing about needing a fresh snapshot first, and no exclusions or prerequisites. The only implicit guidance is "several fields at once," which hints at batching but does not route the agent between alternatives.

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