BootForm

Verify a new email address

bootform_add_verified_email

Starts verifying an email address so it can receive this account's form notifications: emails the address a confirmation link. A person must click that link; then bootform_add_email accepts the address. On an address still pending it sends a fresh link and the earlier one stops working; on an address already verified it sends nothing and answers status "verified".

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": "bootform_add_verified_email"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	The email address to verify

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover safety (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description goes well beyond them: it discloses the outbound email side effect, link invalidation on resend, and the no-op behavior for already-verified addresses. That is exactly the mutation semantics an agent needs before calling.

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?

Three sentences, front-loaded with the core action and flow, and every sentence carries new information about behavior. The final sentence is dense and slightly run-on, packing three conditional cases into one clause chain, which costs a bit of readability.

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 revealing the status value returned for an already-verified address. Given one required parameter and full annotation coverage, nothing an agent needs to call this correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already carries the parameter meaning and the baseline is 3. The description adds only indirect color (the address is one that will receive this account's form notifications) but no format or constraint detail beyond the 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?

States a specific verb and resource — starts verification of an email address by sending a confirmation link — and explicitly separates that from bootform_add_email, which is what actually accepts the address. An agent can distinguish this from sibling add_* destination tools without opening any schema.

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?

Explains the flow prerequisite (a human must click the link before bootform_add_email works) and names the alternative tool. It also covers the two branch conditions: pending addresses resend with the old link invalidated, verified addresses no-op with status "verified".

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?