Formify — AI Assisted E-Signing

Create Draft

create_draft

Create a draft document without sending invitations. Requires fileId from upload_file; templates are not supported for drafts. Signee details, contact methods, signature type, and signature coordinates are optional while drafting. Full validation occurs only when send_draft is called. Call get_file_fields after upload_file if the PDF has form fields that should be pre-filled and saved in the draft. The draft name will become visible to signees when the draft is sent, so it 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. PREVIEW USE CASE: drafts are the recommended way to preview an uploaded document before sending. When the user wants to verify that signature fields, ID scan placeholders, or pre-filled values look correct, build the full configuration here, call get_draft_file_url to retrieve a one-time PDF preview, let the user verify (and adjust via update_draft if needed), then call send_draft to send.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Human-readable draft title that will be visible to signees when sent. 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	Optional form fields to pre-fill and save in the draft. Use exact field names from get_file_fields.
`fileId`	Yes	File ID from upload_file. Required for drafts; templateId is not supported.
`userId`	No	User ID to assign as draft owner. Defaults to the authenticated user.
`language`	No	Language for the eventual signing invitation
`aiAssistant`	No	Optional AI assistant that helps signees while reviewing the document. Requires the aiAssistant capability.
`signeeDetails`	No	Optional list of signees to save in the draft. Entries may be incomplete during the draft phase; fullName and a contact method are required before sending.
`sharingSetting`	No	Whether the draft is private or shared with other users on the account
`personalMessage`	No	Optional personal message for the eventual signing invitation. Maximum 500 characters.
`enableSigningOrder`	No	Enable sequential signing order when the draft is sent (requires signingOrder capability)
`fieldsReadonlyMode`	No	Form field read-only mode. Set to 'filled' when providing pre-filled values that should be locked for signers.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description adds behavioral context not available in the annotations: no invitations are sent at draft time, full validation occurs only when send_draft is called, and the draft name will become visible to signees once sent. These are concrete side effects beyond the metadata flags and do not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Although long, the description is dense with decision-relevant detail: the opening sentence gives the core purpose, the fileId and template constraints follow, and the preview workflow is clearly sectioned. Every sentence earns its place and no fluff is present.

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?

For a tool with 11 parameters, nested objects, zero output schema, and many eligible siblings, the description is unusually complete. It guides the agent through the typical lifecycle: upload_file → get_file_fields → create_draft → get_draft_file_url → update_draft → send_draft, making it clear which prerequisites matter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by tying parameter usage to the document lifecycle: fileId must come from upload_file, fields come from get_file_fields, and signee details are optional at this stage but validated at send_draft. This is workflow-level meaning beyond the raw 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?

The purpose opens with 'Create a draft document without sending invitations,' a precise action, resource, and immediate outcome. It also differentiates the tool from siblings by stating that templates are not supported and that fileId comes from upload_file.

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 explicitly explains when to use drafts: 'Requires fileId from upload_file; templates are not supported for drafts.' It also gives the full workflow for the preview-only case: build configuration here, call get_draft_file_url, let the user verify via update_draft, then call send_draft.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?