Skip to main content
Glama

Wrenform Quick Forms

Create a form without an account

create_quick_form

Create a form without a Wrenform account, using only the email address that should receive submissions. Wrenform emails that address once to confirm. Until it's confirmed, submissions are held and nothing is forwarded. Unconfirmed forms expire after 7 days. Tell the user to check their inbox and click Confirm. Pass framework for the right snippet, and site_url only if the site is already deployed (its https address).

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": {
      "email": "<email>"
    },
    "name": "create_quick_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoDefaults to 'Contact form'.
emailYesThe address that should receive the form's submissions.
site_urlNoThe deployed site's https address, e.g. https://example.com; it becomes the only allowed origin. Omit it if the site isn't deployed yet (a localhost address is ignored).
frameworkNoThe site's framework. html needs no JavaScript.html

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by describing the entire lifecycle: Wrenform emails a confirmation, submissions are held and nothing is forwarded until confirmed, and unconfirmed forms expire after 7 days. This is exactly the kind of consequence-level context an agent cannot get from readOnlyHint/openWorldHint alone.

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?

Four sentences, front-loaded with the account-free premise, then the confirmation consequence, then the parameter rules. No filler; each sentence carries a distinct operational fact.

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?

With no output schema, the description should hint at what comes back; 'for the right snippet' implies a code snippet is returned, but the actual return payload (snippet, form identifier, confirmation state) is never stated. Otherwise the workflow, timing, and expiry are complete for a 4-parameter creation tool.

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 coverage is 100%, so the baseline is 3; the description earns a bump by explaining why `framework` matters ('for the right snippet') and reinforcing the deployment precondition for `site_url`. The `site_url` guidance largely duplicates the schema text, and `name` is never discussed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a form') plus the distinguishing constraint that no Wrenform account is needed, with the email address as the sole requirement. It clearly separates this from account-based flows, though it never names a sibling like check_quick_form, which would make differentiation explicit.

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?

Gives concrete conditional guidance for parameters ('Pass framework for the right snippet, and site_url only if the site is already deployed') and a follow-up instruction ('Tell the user to check their inbox and click Confirm'). It lacks an explicit when-to-use-this-vs-alternative statement, so the agent must infer that confirmation status is checked elsewhere.

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