Formesign

Create and PUBLISH a new live form in one step. This is the ONLY tool for creating a form. Use it in every case: 1. The user uploaded, attached, or pasted a file, document, image, screenshot, or PDF: convert that content into the "document" parameter. 2. The user described the form in words (e.g., "create a feedback form", "make a registration form") or you worked out the fields together in conversation: write the complete form yourself as the "document" parameter, with a title, sections, and every field with its label, input type, and choices, then call this tool. Do NOT ask the user to review an outline first unless they ask for one. If they do, agree the fields in chat, then call this tool once. Use "html" format when the content has layout, formatting, structure, or comes from HTML, SCREENSHOT, IMAGE, or PDF. Use "markdown" format when the content is plain text without formatting. This tool returns the complete published form with all sections and fields, a preview URL, and an edit URL. IMPORTANT: This tool already renders the preview widget for the newly created live form, so do NOT call preview in the same turn after a successful create_form. That would render the preview UI twice. Call create_form at most once per turn. To change the form afterwards, use update_form with the returned publishId. IMPORTANT: Do NOT include sensitive personal data in the document content. This includes health information, biometric data, social security numbers, payment card industry information (credit/debit card numbers, CVV, expiration dates), bank account details, login credentials, passwords, or authentication secrets. Remove or redact any such sensitive data before passing the document. Output MUST match the "format" parameter. Never mix formats. FIELD DETECTION (when the document comes from a user-supplied source; when you are writing the document yourself from a description, include every field the user asked for): - Create a form field ONLY where the source document has an actual place to write, mark, check, or sign: a blank line (____), an empty box, a checkbox, or a signature line. The number of fields must match the number of real inputs in the source — do not add one. - Text that has NO input in the source (paragraphs, recitals, numbered clauses, instructions) is descriptive content. Keep it as headings/<p> text in the form, NOT as a field. Do not attach an input box to a clause that the source only asks the reader to read. - Reproduce all wording VERBATIM. Never paraphrase, summarize, shorten, or rewrite the source text — especially legal, consent, agreement, or policy text. - Preserve the source's own section order and grouping. Do not split one block into many sections or invent sections. SIGNING DOCUMENTS (formesign is an e-signature app): When the source is an agreement, waiver, consent, release, contract, or any document meant to be SIGNED, keep the document whole — its clauses and paragraphs are content to be signed as one agreement, not separate questions. The only fields are the actual fill-in spots in the source: - A signature line (e.g., "Signature ____") → a signature field. Label it "Signature" (or "Parent/Guardian's Signature", etc., matching the source). Do not turn a signature line into a generic text question. - A date line next to a signature → a date field. - Name / relationship / other labeled blanks → text fields. Keep separate signer blocks (e.g., participant vs. parent/guardian) as separate sections, in source order.

create_form

Edit a LIVE, already-published form by applying a natural-language instruction (e.g., "add a phone number question", "rename the feedback section", "remove the optional consent field"). This is the tool to use when the user wants to change an existing published form — it modifies the real, live form that respondents see. If you don't know the publishId, use list_forms first to find it by title. This tool changes the form's CONTENT only: its questions, sections, choices, and text. It cannot change settings such as email notifications, signature workflow, payments, Google Drive sync, HIPAA, or the business name; for those use progress. Returns the preview UI of the updated form. IMPORTANT: This tool already renders the preview widget for the updated live form, so do NOT call preview in the same turn after a successful update_form — that would render the preview UI twice. Call update_form at most once per turn.

update_form

Use this to help the user turn on, set up, or change a form's SETTINGS: everything about how a published form behaves that is not one of its questions. It opens the setup checklist, which is where the user enables each setting (for example email notifications), and returns checklist status plus next actions. This is the ONLY tool for these settings, so never reply that no tool exists for them. ALWAYS use this tool when the user's message is about ANY of these topics — regardless of how they phrase it: TOPICS THIS TOOL OWNS: - Email notifications (submission alerts, owner/admin notify, respondent confirmation, completion emails, signature workflow emails) - Signature and workflow setup - Payment enablement - HIPAA compliance configuration - Google Drive sync for signed documents - Respondent or customer mapping - Business name setup - Score setup - Submit message or form layout customization - General "what's next" or "what's left to configure" for a form If the user's intent touches any of the above topics — whether they are asking how to, asking if it's possible, reporting it's not working, or just mentioning the topic — use this tool first before responding. NOT THIS TOOL: adding, removing, rewording, reordering, or restyling the form's questions, sections, choices, or text (including "make it a quiz" or "make it more engaging"). Those change the form's content, so use update_form. Creating a new form is create_form.

progress

Fetch the full structure of a LIVE, already-published form by publishId — including title, sections, fields, field types, choices, and required flags. Use this to understand what a form contains BEFORE editing it with update_form, or to answer questions about the form's shape. If you do not know the publishId, use list_forms first to find it by title. Does not return submissions — use list_submissions for that.

get_form

Search and list the user's published forms with optional filters for title, date range, submission count, ordering, and pagination. Use this tool to find a form (and its publishId) by name or criteria before invoking any other tool that requires a publishId (such as update_form). Submissions are not a form type — this tool does not search submissions. Returns the matching forms as structured data (id, publishId, title, url, submission_count) for the model to present.

list_forms

Show the preview UI for a single form when the user wants to see, show, open, view, or preview it (e.g., "show me my feedback form", "show me the preview"). Pass publishId for the form (use list_forms first if you do not know it). Do NOT call this in the same turn as create_form or update_form, because those already render the preview widget. Call this at most once per turn. To list or search across multiple forms, use list_forms instead.

preview