Skip to main content
Glama

Fill in a form

cotlet_browser_fill_form
Destructive

Fills several fields in one step: text fields take text, drop-downs an option's label, checkboxes, radios and switches true or false. Stops at the first field that fails and names those filled. Does not send the form: click its button after. Answers the page after it: the elements and text in view, with the same numbers.

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": "cotlet_browser_fill_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoLeave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
tabNoThe Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.
dialogNoHow to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
fieldsYesThe fields in the order a person fills them.
dialog_textNoText for a prompt dialog this step opens; implies accept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tab
      Added value: +{
      +  "description": "The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true, and idempotentHint=false, so safety is covered structurally; the description earns credit for disclosing failure semantics beyond that — it stops at the first failing field and reports which fields were already filled, which is the key partial-mutation behavior an agent must plan around. It also documents the return payload (page elements and text "with the same numbers") in the absence of an output schema. It stops short of explaining why the operation is destructive or what page-side side effects (onchange handlers, validation) filling may trigger.

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?

Three compact sentences, each carrying distinct information: what it does, how it fails and what it returns, and what it deliberately does not do. The constraint that matters most for correctness (it does not submit) is called out directly rather than buried.

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 5-parameter mutation tool with no output schema, the description covers the essentials: field-type/value mapping, first-failure behavior, the no-submit boundary, and the shape of the answer. Minor gaps remain around destructive side effects and whether partial fills leave the page in a modified state the caller must clean up.

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

Parameters4/5

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

With 100% schema coverage the baseline is 3, but the description adds value by mapping the polymorphic `value` field to field types — text fields take text, drop-downs take an option's label, checkboxes/radios/switches take true or false — which the schema only vaguely calls "Text, option, or true/false." That mapping is the most likely source of invocation error and is spelled out here.

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?

"Fills several fields in one step" names a specific verb and a batch resource, and immediately enumerates the field kinds it handles (text, drop-down, checkbox, radio, switch), which separates it from the single-element siblings like cotlet_browser_type and cotlet_browser_select. It also states the terminal boundary — it does not submit — so an agent knows exactly where this tool's authority ends.

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: batch filling in one call, and explicitly routes the submit step to the click tool ("Does not send the form: click its button after"). It does not name the single-field alternatives by name or say when a one-field edit should use them instead, so the routing is strong on the submit side but implicit on the granularity side.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources