Formify — AI Assisted E-Signing

Create Document

create_document

Destructive

Create a document and send it for electronic signature. Provide either templateId (from list_templates) or fileId (from upload_file) — not both. When using a template: call get_template to see signee slots and pre-configured signature settings, then get_template_fields for form fields. When using a file: call get_file_fields to discover form fields. Signature placement defaults to new_page unless explicitly configured via signatureBox. The document name is visible to signees and should be a clear, human-readable title, not the uploaded filename. If deriving it from a PDF filename, strip the file extension unless the user explicitly wants to keep it. BEFORE calling this tool, always ask the user: (1) invitation language, (2) optional personal message, (3) signature placement — only when using a file, not a template: new_page (default, recommended) or existing page with coordinates, (4) signature type — only if get_account_capabilities shows non-default types available and no template default applies; the choice only selects how the signer will verify on Formify's signing page, (5) AI assistant — only if get_account_capabilities confirms the aiAssistant capability. ALSO when using a file: ask the user whether they want a preview before sending. If yes, save the configuration as a draft via create_draft, share a one-time preview via get_draft_file_url, and send via send_draft after the user confirms — instead of calling create_document directly. Recommend a preview whenever signaturePlacement is 'existing' or when custom coordinates have been used.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Human-readable document title visible to signees. If deriving from an uploaded PDF filename, strip the file extension (e.g. 'contract.pdf' → 'contract') unless the user explicitly wants the extension.
`fields`	No	Form fields to pre-fill at document creation time. This is the preferred way to fill fields — always use this when you have the values, rather than set_document_field_values after creation.
`fileId`	No	File ID from upload_file. Required if templateId is not provided.
`userId`	No	User ID to assign as document owner. Defaults to the authenticated user.
`language`	No	Language for the signing invitation
`templateId`	No	Template ID from list_templates. Required if fileId is not provided.
`aiAssistant`	No	Optional AI assistant that helps signees while reviewing the document. Requires the aiAssistant capability.
`signeeDetails`	Yes	List of signees. At least 1 is always required. The number of signees should match what the template expects — call get_template first to see how many signee slots it defines. The user decides the final count; some templates are pre-configured for a specific number.
`sharingSetting`	No	Whether the document is private or shared with other users on the account
`personalMessage`	No	Optional personal message included in the signing invitation. Maximum 500 characters.
`enableSigningOrder`	No	Enable sequential signing order (default false)
`fieldsReadonlyMode`	No	Always set to 'filled' when providing field values — this locks pre-filled fields so signers cannot change them. Options: keepOriginal (default — no locking), filled (pre-filled fields become read-only), all (all fields become read-only).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 22, 2026

changedInput schema / properties / signeeDetails / items / properties / idScanBox / description

Previous value: -"ID scan placeholder coordinates. Required for digital_ink_id_scan unless a template already provides a pre-configured position. Omit unless overriding."New value: +"ID scan placeholder coordinates. Required for digital_ink_id_scan unless a template already provides a pre-configured position. Omit unless overriding. The ID document itself is captured and read on Formify's signing page; only the placeholder's position is configured here, and no image or document data passes through this API."

changedInput schema / properties / signeeDetails / items / properties / signatureType / description

Previous value: -"Signature method: digital_ink (default, always available), bankid_identification (Swedish BankID — requires signatureBankId capability), digital_ink_id_scan (draw + ID scan — requires signatureIdScan capability), face_liveness (draw + face liveness — requires signatureFaceLiveness capability). Call get_account_capabilities to verify availability before using a non-default type. Omit when using a template to use its pre-configured method. Only set to override."New value: +"Signature method: digital_ink (default, always available), bankid_identification (Swedish BankID — requires signatureBankId capability), digital_ink_id_scan (draw + ID scan — requires signatureIdScan capability), face_liveness (draw + face liveness — requires signatureFaceLiveness capability). Call get_account_capabilities to verify availability before using a non-default type. Omit when using a template to use its pre-configured method. Only set to override. Identity verification for bankid_identification, digital_ink_id_scan and face_liveness is performed by Formify's signing page in the signer's browser, after the invitation is sent. This parameter only selects the method: no identity document, biometric data or national identity number is sent to, returned by or stored through this API."

First observedSep 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description discloses key behavioral traits beyond the annotations: it explicitly states that the document is sent for electronic signature, that identity verification happens on Formify's signing page (not via this API), and that no image/document data passes through for ID scan. It also clarifies that only the signature method is selected, not the verification itself. These details add significant value over the annotations (readOnlyHint=false, destructiveHint=true) and help the agent understand side effects and privacy implications.

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?

The description is long (~250 words) but appropriately so for a tool with 12 parameters and complex nested objects. It is front-loaded with the core action and then cascades into conditions and user-interaction steps. While somewhat verbose, every sentence conveys necessary guidance, and the structure (core action → prerequisites → user questions → preview workflow) is logical. Slightly more concise would be ideal, but given the complexity, a 4 is justified.

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?

The description covers prerequisites, alternatives, user interaction requirements, and behavioral side effects thoroughly. The main gap is the absence of any mention of the tool's return value (e.g., document ID or URL) and potential error conditions. Since there is no output schema, the agent must infer what the tool returns. While not critical for calling correctly, this omission prevents full completeness for a tool of this complexity.

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?

The input schema has 100% coverage, with extensive per-parameter descriptions (e.g., the field value rules, coordinate calculations, signatureType capability requirements). The description adds minimal parameter semantics beyond stating the templateId/fileId exclusivity and advising to strip file extensions from names. Since the schema already documents every parameter in depth, the description's added value is limited, warranting the baseline score of 3.

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?

The description clearly states the action: 'Create a document and send it for electronic signature.' It explicitly distinguishes from siblings by noting the template/file exclusivity and referencing create_draft as an alternative when a preview is desired. The verb and resource are specific, making it immediately clear what this tool does versus create_draft, create_link, or create_template.

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?

The description provides explicit usage guidance: when to use templateId vs fileId, mandatory preliminary calls (get_template, get_template_fields, get_file_fields), and a detailed list of questions the agent must ask the user before calling. It also explains when to use create_draft and send_draft instead of create_document, and when to recommend a preview. This is comprehensive, actionable, and leaves no ambiguity about when to use this tool versus alternatives.

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

All Formify — AI Assisted E-Signing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?