What We Shipped
We put it on our own contact form
Our contact form below exposes three WebMCP tools alongside the regular Send button. Filling the form and sending it are separate actions, and submission still requires Cloudflare Turnstile verification.
// fill_contact_form: populates the form, does not send
// wait_for_contact_verification: waits for the Turnstile token
// submit_contact_form: sends, same endpoint the button uses
await document.modelContext.registerTool({
name: "fill_contact_form",
description: "Fill the Paniolo contact form fields on this page...",
inputSchema: { /* name, email, org, type, message */ },
execute: async (input) => fillContactForm(input),
});
In our end-to-end test with a WebMCP-capable browser, the fields filled visibly, the Turnstile widget showed "Success," and the page confirmed "Message sent." The tools use the same submission endpoint and server-side verification as the human interface.
The important work was deciding what each tool should do, how to describe it, and what happens when validation or verification fails. Those decisions connect the knowledge an agent needs with the harness it acts through.
In a supported browser with site tools enabled, you can ask your agent to fill this form with details you provide, then review the fields before asking it to send. The badge indicates that the page has registered tools; completing the workflow also depends on your agent's support and verification succeeding.