Skip to main content
Glama
rlgrpe

camoufox-mcp

by rlgrpe

browser_fill_form

Fill multiple form fields such as textboxes, checkboxes, radios, comboboxes, and sliders by providing field references and values.

Instructions

Fill multiple form fields.

    Args:
        fields: List of form fields to fill. Each field should have:
               - name: Human-readable field name
               - ref: Exact target field reference from the page snapshot
               - type: Field type (textbox, checkbox, radio, combobox, slider)
               - value: Value to fill (for checkbox use 'true'/'false',
                       for combobox use option text)

    Returns:
        Success message with filled fields
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It does not mention prerequisites (e.g., page snapshot needed), side effects (e.g., does it clear existing fields?), or error scenarios. This is insufficient for a form-filling tool.

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?

The description is a well-structured docstring with Args and Returns sections. It is concise and front-loads the purpose. Minor improvement could be removing the Returns section if output schema is present, but it remains clear.

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?

The tool has one parameter with 0% schema coverage, no annotations, and an output schema (not shown). The description adequately explains parameter semantics and return value, but lacks behavioral context (prerequisites, side effects, error handling). It is minimally complete.

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?

The input schema has 0% description coverage, but the description compensates by explicitly listing expected keys (name, ref, type, value) and providing type-specific value instructions. It adds significant meaning beyond the schema, which only defines a generic array of objects.

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 verb 'fill' and resource 'multiple form fields'. It distinguishes from siblings like browser_type (single field) and browser_click (clicking).

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 provides detailed Args instructions but does not explicitly state when to use this tool over alternatives (e.g., browser_type for single fields, browser_select_option for dropdowns). Usage context is implied but not stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rlgrpe/camoufox-mcp-python'

If you have feedback or need assistance with the MCP directory API, please join our Discord server