Skip to main content
Glama

fill_form

Populate multiple form fields by stable ID in one call, with dry-run preview or submit, to automate web form entry.

Instructions

Fill {id: value}; submit=true submits. dry_run previews.

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
expectNo
fieldsYes
submitNo
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/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 real behavior: submit=true causes submission and dry_run previews the effect. However, it omits whether submission is irreversible, whether filling triggers validation or side effects, and what the call returns.

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?

Three compact clauses, front-loaded with the primary operation and followed by the two flags. It is telegraphic but free of waste; the terseness costs clarity rather than padding.

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?

For a mutation tool with no annotations, no output schema, a nested object parameter, and 0% schema description coverage, this is too thin. Key gaps include the undocumented `expect` parameter, the meaning of non-boolean `submit` values, and the post-submit outcome.

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 coverage is 0% across 4 parameters. The description explains the `fields` mapping format, `submit=true`, and `dry_run`, but leaves `expect` completely undefined and does not explain why `submit` accepts boolean, integer, or string values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Fill {id: value}" names a specific verb and the shape of the payload, but never says what is being filled (a form on the current page) or how it differs from the sibling `act`. The purpose is inferable from the tool name more than from the description text.

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?

It explains what two parameters do (submit, dry_run) but gives no when-to-use guidance, no prerequisites, and no comparison to alternatives such as `act` or `open`. An agent must guess whether this tool also handles navigation or clicks.

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

Deploy Server

Other Tools