Skip to main content
Glama

test_form

Fill a web form by matching field names or placeholders, type values, click the submit button, and verify the result matches expected success, validation error, or any outcome.

Instructions

Fill a form, submit it, and verify the result — all in one call.

Matches fields by name/placeholder, types values, clicks submit, then checks if the operation succeeded or failed as expected.

Args: form_fields: Dict mapping field name to value. Example: {"email": "test@test.com", "password": "abc123"} submit_text: Text of submit button to click. Auto-detects if empty. submit_index: Element index of submit button. Used if submit_text is empty. expected_result: "success" (expect redirect/success msg), "validation_error" (expect error msg), or "any"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
form_fieldsYes
submit_textNo
submit_indexNo
expected_resultNosuccess

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It details how fields are matched, values typed, submit clicked, and result checked. It also mentions auto-detection and fallback behavior for submit button parameters.

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 well-structured with a concise overview followed by detailed Args. It is front-loaded with the main purpose. A few minor redundancies exist, but overall efficient.

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?

Given the tool has an output schema, the description need not detail return values. It covers all input parameters thoroughly and provides examples. The behavioral description is sufficient for a testing tool.

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

Parameters5/5

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

Schema coverage is 0%, so description must compensate. It explains form_fields with example, submit_text as button text, submit_index as element index, and expected_result as an enum with three values. This adds significant meaning beyond the raw schema.

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 fills a form, submits it, and verifies the result. The verb 'Fill' and resource 'form' are specific, and the composite nature distinguishes it from simpler sibling tools like click or type_text.

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?

The description implies using this tool for form submission with verification, but does not explicitly compare alternatives or state when not to use it. The embedded parameter documentation (e.g., auto-detection of submit button) provides implicit guidance.

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/chriswu727/argus'

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