Skip to main content
Glama
Sign In
dawg-mcp

dawg-mcp

by dawgswarm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

browser_fill_form

Fill multiple browser form fields in one call by providing a list of elements with descriptions, references, and values. Returns an updated AI snapshot.

Instructions

Fill multiple form fields in one call.

fields is a list of {"element": desc, "ref": ref, "value": value}. Returns a fresh AI snapshot.

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

Input Schema

NameRequiredDescriptionDefault
fieldsYes
session_idNo

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 full burden. It usefully notes 'Returns a fresh AI snapshot' but omits details like whether the form is submitted, validation behavior, or session requirements. The behavioral disclosure is partial.

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?

Excellent conciseness: two sentences, front-loaded with the core purpose, followed by a structured definition of the main parameter. No wasted words.

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?

Given no output schema, no annotations, and two parameters, the description provides the essential purpose and fields format but lacks context on session_id, prerequisites, and when to use this vs. sibling tools. It meets minimum completeness but has clear gaps.

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?

Schema description coverage is 0%, so description must compensate. It explains the fields parameter format with a specific structure (`{"element": desc, "ref": ref, "value": value}`), adding meaning beyond the schema. However, the session_id parameter is not 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 clearly states the tool's action ('Fill multiple form fields') and its batch nature ('in one call'). It distinguishes itself from siblings like browser_type (single field) and browser_click (clicking) by specifying multiple fields at once.

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?

The description implies use for efficiency ('in one call') but does not explicitly state when to prefer this over browser_type or any prerequisites. No guidance on when not to use it.

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