BootForm

Create a form

bootform_create_form

Creates a new form on the connected account and returns its id, endpoint and a ready-to-paste HTML snippet to put on the person's page. To change a form that already exists, use bootform_configure_form instead (bootform_list_forms shows what exists). Form names don't have to be unique. Without workspace_id the form goes to the account's default workspace. Creating forms is rate limited: RATE_LIMITED means wait a little and try again.

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

Input Schema

Name	Required	Description
`name`	Yes	Display name for the form
`redirect_url`	No	Optional post-submission redirect URL
`workspace_id`	No	Optional workspace to create the form in (bootform_list_workspaces); omitted, it goes to the default workspace
`allowed_origins`	No	Optional origin allowlist

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: name uniqueness is not enforced, the return payload includes a ready-to-paste HTML snippet, and rate limiting surfaces as a RATE_LIMITED error with retry guidance. The annotations already cover the mutation/safety profile (non-readOnly, non-destructive, non-idempotent), so the retry and non-uniqueness notes are the value-add and they are present.

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?

Four sentences, front-loaded with purpose and value of the return, with routing and rate-limit info after. Slightly redundant where it re-explains the workspace_id default that the schema already documents, but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by naming the return fields including the HTML snippet. Combined with the rate-limit error code, non-unique names, and default workspace behavior, an agent has everything needed to call and handle the result.

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%, so all four parameters are already documented, including the default-workspace fallback for workspace_id. The description's mention of workspace_id only restates what the schema already says, so it adds no new parameter semantics; baseline 3 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?

Opens with a specific verb and resource ('Creates a new form on the connected account') and goes further by naming what the call returns (id, endpoint, HTML snippet). It explicitly distinguishes itself from bootform_configure_form and bootform_list_forms, so an agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-not with the alternative named ('To change a form that already exists, use bootform_configure_form instead'), plus a discovery pointer to bootform_list_forms. It also states the workspace_id omission behavior, which is the main usage decision an agent must make.

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

All BootForm tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?