Skip to main content
Glama

smart_fill_form

Fills multiple form fields at once—inputs, selects, checkboxes, editors, Shadow DOM/iframe fields, and file uploads—then stops before submit by default.

Instructions

Fill several fields at once: inputs, editors, comboboxes, selects, checkboxes, Shadow DOM/iframe fields, file uploads. Stops before Submit by default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "smart_fill_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
mainNo
gmailNo
tabIdNo
fieldsNo
overwriteNo
snapshotModeNo
returnSnapshotNo
snapshotMaxCharsNo
stopBeforeSubmitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.1
    • addedInput schema / properties / fields / items / properties / all
      Added value: +{
      +  "description": "When true, fill all matching controls across frames instead of only the best match.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fields / items / properties / check / description
      Added value: +"true/false sets a checkbox/radio; label(s) check matching options."
    • changedInput schema / properties / fields / items / properties / check / oneOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +]
  2. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation profile is partially covered. The description adds the important behavioral trait that submission is withheld by default, but says nothing about whether filling fires input/change events, what happens on overwrite conflicts, or how frames are traversed.

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 scope, then the key safety default. No filler.

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

Completeness2/5

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

This is a high-complexity tool with nine parameters, nested objects, and no output schema, yet the description explains only the taxonomy of fillable controls and the submit default. Critical parameters governing overwrite behavior and snapshot return are left entirely to an undocumented schema, so an agent cannot confidently construct a call.

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

Parameters2/5

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

Schema description coverage is 0% across 9 top-level params and a 14-key nested field object. The description implies that value/check/option/file/keys map to the listed control types, and 'Shadow DOM/iframe' loosely gestures at frameIdx/all, but it never explains ref vs selector, overwrite, returnSnapshot, snapshotMode, snapshotMaxChars, tabId, or the puzzling main/gmail properties.

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 opens with a specific verb and resource ('Fill several fields at once') and enumerates the control classes it handles (inputs, editors, comboboxes, selects, checkboxes, Shadow DOM/iframe, file uploads). It clearly separates itself from single-action siblings like act_fast by emphasizing multi-field filling, though it never names an alternative.

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?

'Fill several fields at once' implies the batch-prefill scenario and 'Stops before Submit by default' signals the safe-preview posture. However, there is no explicit when-not guidance, no mention of when to prefer act_fast or batch_actions, and no prerequisites stated.

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