Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Fill Form

fill_form

Fills multiple form inputs in one call by fuzzy-matching labels to placeholders, aria-labels, or labels. Use it to populate several fields at once instead of one round-trip per input.

Instructions

Fill N inputs from {label:value} in one call. Labels fuzzy-match placeholder/ aria-label/. Beats N aria_type round-trips.

Ex: fill_form('t0', {'email':'a@b.c','password':'hunter2'}) → {"filled":["email","password"],"missed":[]}

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

Input Schema

NameRequiredDescriptionDefault
clearNo
fieldsYes
tab_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 behavioral burden. It usefully discloses fuzzy label matching against placeholder/aria-label/<label> and that missed fields are returned, but it omits the important semantics of the clear parameter defaulting to true and whether existing input values are erased.

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?

The description is front-loaded and compact: two sentences plus a short example. Every part earns its place by stating the batch behavior, matching semantics, alternative it replaces, and an illustrative call with result shape.

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?

An output schema exists, so the description need not explain return values, though the example does. However, for a mutation tool with no annotations, the description omits the clear-before-fill behavior and any side-effect or failure semantics, leaving notable gaps.

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 0%, so the description must compensate. It explains the fields parameter as a {label:value} map and shows tab_id positionally via the example, but the clear boolean parameter is never mentioned or explained.

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?

The description states a specific verb and resource: fill N inputs from label/value pairs in one call. It distinguishes itself from the sibling aria_type by explicitly claiming it beats N aria_type round-trips, so an agent can tell when this batch tool is preferable.

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?

It gives clear usage context by contrasting the tool with repeated aria_type calls, implying it should be used for multi-field form filling. It does not state explicit exclusions or prerequisites, so it falls short of the top score.

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