Skip to main content
Glama

List the forms on a web page

forms
Read-only

List the forms on a web page: action URL, method, fields (name, type, label, required) and a guess of each form's purpose (login, signup, newsletter, search, contact, payment). Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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": {
      "url": "<url>"
    },
    "name": "forms"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely useful operational context beyond them: typical latency (1-3 s), a concrete free quota (20 calls/day per user), the metered price ($0.002/call via x402 in USDC on Base), and the expectation that the first unpaid call returns pricing requirements. It stops short of saying what happens on non-HTML or JS-rendered pages where no forms are discoverable.

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?

Front-loaded with the returned data first, then cost. Efficient and scannable, though the pricing sentences take roughly as much space as the functional description and could be compressed without losing meaning.

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?

There is no output schema, so the description correctly spells out the return shape, and it covers cost/auth mechanics for the payment parameter. Missing only edge-case behavior (pages with no forms, client-rendered forms, blocked URLs) that would matter for an open-world fetch tool.

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 coverage is 100% and both parameters are documented in-schema, including the payment flow (omit on first call, supply base64 PAYMENT-SIGNATURE afterwards). The description's pricing sentence corroborates the payment model but adds no syntax or format detail beyond the schema, so the baseline applies.

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 opens with a specific verb and resource ('List the forms on a web page') and enumerates exactly what is returned: action URL, method, per-field name/type/label/required, plus an inferred purpose category. That is far more specific than the title alone and clearly separates it from generic page-content siblings like page_markdown or page_text.

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?

Usage is implied by the purpose statement (use this when you need form structure rather than page content), but the description never states when to choose it over alternatives or when it is inappropriate. No exclusions, no prerequisites about the page needing to be public or statically rendered.

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.