Skip to main content
Glama

Wrenform Quick Forms

Get a form snippet

get_snippet
Read-onlyIdempotent

Get ready-to-paste code for a form in a given framework: html (no JavaScript), html_strict_csp, fetch, nextjs, astro, react, vue, nuxt, svelte, hugo, jekyll, framer, webflow. Insert it into the site as returned; it already includes the spam honeypot.

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": {
      "form_id": "<form_id>"
    },
    "name": "get_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
form_idYesThe form's ID, as returned by list_forms or create_form (12 letters and digits).
frameworkNoThe site's framework. html needs no JavaScript.html

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the returned snippet already includes the spam honeypot and must not be altered before insertion. It does not cover error cases for invalid form_id or unknown framework.

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?

A single compact sentence that front-loads the purpose and then the supported variants. The honeypot caveat is appended where it matters, and there is no filler wording.

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 usefully characterizes the return value as paste-ready code that includes the honeypot. It is complete enough for a two-parameter, fully documented read tool, though it omits what happens on an invalid form_id or an unsupported combination.

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 description coverage is 100%, with both form_id and framework fully documented including the enum and default, so the baseline is 3. The description's framework list merely restates the enum, and 'html needs no JavaScript' is already in the schema; it adds little analytical meaning beyond the structured fields.

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?

States a specific verb ('Get'), a specific artifact ('ready-to-paste code for a form'), and enumerates the frameworks it supports. This is clearly distinguishable from get_docs, check_quick_form, and create_quick_form, none of which produce embed code.

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 only implied: the agent can infer this is called once a form exists and needs embedding. There is no explicit statement of when to prefer this over siblings or what preconditions (e.g., form must be published) apply. The instruction 'Insert it into the site as returned' guides what to do with the output rather than when to call the tool.

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