Skip to main content
Glama

fill_form

Fills multiple form fields in order—text inputs, selects, checkboxes and radios—in a single call, stopping at the first failure and reporting each field's outcome.

Instructions

Fills several fields in one call, in order: text fields and s as fill_input does; a checkbox or radio takes 'true' or 'false' and is clicked only when its state differs. Returns each field's outcome (filled, selected, checked, unchecked, unchanged), never the values; stops at the first failing field, naming it and what was done.

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
fieldsYes1 to 50 fields, filled in order.
tab_idNoDefault: the active tab.
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A4.2/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 so well: it discloses fill ordering, conditional clicking for checkboxes/radios ('clicked only when its state differs'), the per-field outcome vocabulary, that values are never returned, and the first-failure stop. The notable gap is that it doesn't say whether fields already filled before the failure remain filled or are rolled back.

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?

A single compact passage that leads with the core action and then layers ordering, value semantics, return shape, and error behavior. Nearly every clause carries distinct information with no filler.

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?

For a tool with no annotations and no output schema, the description covers the important ground: what gets filled, in what order, what the return outcome labels are, and how failures surface. The remaining ambiguity is partial-fill state after a mid-sequence failure, which matters for an agent deciding whether to retry.

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 100%, so the baseline is 3; the schema already documents selector formats, the 'true'/'false' checkbox convention, and the 1–50 field limit. The description's extra contribution is mostly behavioral (ordering, conditional click) rather than adding new meaning to individual parameters.

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 and resource ('Fills several fields in one call') and immediately differentiates itself from the sibling fill_input by describing itself as the batch equivalent ('as fill_input does'). An agent can tell exactly what this does without opening the schema.

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

Usage Guidelines4/5

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

The batch framing ('several fields in one call, in order') makes the when-to-use condition clear relative to the single-field fill_input, and the failure behavior ('stops at the first failing field') helps an agent plan sequencing. However, it never explicitly says to prefer fill_input for a single field or when not to use this tool.

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