Formify — AI Assisted E-Signing

Get Draft File URL

get_draft_file_url

Read-onlyIdempotent

Get a short-lived, one-time-use download URL for a PDF preview of the draft with signature fields rendered at their configured coordinates. Returns JSON with downloadUrl + fileName + mimeType + expiresInMinutes. The user opens the URL in a browser; no Authorization header is required. Use this when the MCP client should hand the user a clickable link. If the client can render PDFs inline, prefer get_draft_file (returns the PDF as an embedded resource via the session Bearer token). Typical preview flow: create_draft → get_draft_file_url (or get_draft_file) → user reviews PDF → (optional update_draft and re-fetch) → send_draft. Fields without valid coordinates (page, x, y) are not rendered in the PDF but remain in the draft data. The URL expires after 10 minutes and is consumed on successful download. The draft must still have status draft and must not be expired.

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": {
      "draftId": "<draftId>"
    },
    "name": "get_draft_file_url"
  }
}

Input Schema

Name	Required	Description	Default
`draftId`	Yes	Unique identifier of the draft to preview

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?

Although annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, the description adds substantial behavior beyond them: the URL is short-lived and one-time-use, expires after 10 minutes, is consumed on successful download, requires no Authorization header, and only works while the draft is still in draft status and not expired. It also discloses that fields without valid coordinates are omitted from the PDF but remain in draft data.

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?

The description is front-loaded with the core purpose and return shape, then moves through usage, alternative selection, workflow, rendering caveats, expiry, and preconditions. Although detailed, each sentence carries distinct operational information and there is no filler or repetition.

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?

There is no output schema, but the description enumerates the returned JSON fields (downloadUrl, fileName, mimeType, expiresInMinutes) and explains auth behavior, expiry, one-time use, and draft preconditions. Given the single-parameter schema and annotations, this is complete enough for an agent to invoke the tool correctly.

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% and the single draftId parameter is already documented in the schema, so the schema does the heavy lifting. The description adds a relevant precondition for draftId validity—the draft must still have status draft and must not be expired—but does not add format or lookup semantics for the identifier itself.

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 states a specific verb and resource: get a short-lived, one-time-use download URL for a PDF preview of a draft. It also distinguishes this from the sibling get_draft_file by explaining that this tool is for handing the user a clickable link, while get_draft_file is for clients that can render PDFs inline.

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?

It gives explicit usage guidance: use this when the MCP client should hand the user a clickable link, and prefer get_draft_file if the client can render PDFs inline. The typical preview flow further clarifies where this tool fits among create_draft, update_draft, and 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

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?