Skip to main content
Glama

Docflare

Prepare a document

prepare_document
DestructiveIdempotent

Manages who gets a draft and how it is sent: its name, who signs it and who gets a copy, by email (people new to Docflare are added to the recipients), and delivery, email, signing order, expiry, reminders and what recipients may download. Only what is sent changes; everything left out stays as it is, and settings never set take the workspace defaults. It covers any of these changes, such as "make it expire in 7 days". More signers or CCs than the plan allows are refused, naming the emails that do not fit, and nothing changes. It places no fields: a signer needs at least one, such as a signature, which edit_document places, and edit_document also sets whether signers share one copy or each get their own. On a document the user signs themselves (signed_by_sender), everyone listed gets the signed copy by email, and only the name, subject and message apply. flow switches a draft between the two, starting fresh with no recipients or fields: when the user wants to sign a signature request themselves, or have others sign a document meant for them. Nothing is sent. The answer is a preview of exactly what send_document would send, text_changes included, a preview_url that shows the pages as a signer will see them, and a review_token for send_document when nothing blocks the send.

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": {
      "id": "<id>"
    },
    "name": "prepare_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe document id from the upload_document answer.
flowNoSwitches the draft: sign-document when the user signs it themselves and sends the signed copy, get-signature when others sign it. Switching starts fresh: its recipients and fields are removed and its text stays, so send recipients with it. Leave out to keep it.
nameNoA new name for the document, shown to recipients. Leave out to keep the current name.
messageNoThe invitation email message. It may use {sender.name}, {sender.email}, {document.name} and no other variable. The workspace default when left out.
subjectNoThe invitation email subject. It may use {sender.name}, {sender.email}, {document.name} and no other variable. The workspace default when left out.
deliveryNoemail sends each signer an invitation, link gives the user signing links to share. email when left out.
remindersNoWhether Docflare reminds signers who have not signed yet.
recipientsNoEveryone who receives the document, replacing the current recipients. Leave out to keep them.
reminder_maxNoHow many reminders at most.
signing_orderNotrue when signers sign one after another, in the order of recipients. Everyone signs at once when left out.
allow_downloadNoWhether recipients may download the signed document.
expires_after_daysNoDays until the signing links stop working. The workspace default when left out.
warn_before_expiryNoWhether signers are warned before the links expire.
attach_pdf_to_emailsNoWhether the signed PDF is attached to the completion emails. Needs allow_download.
reminder_every_hoursNoHours between reminders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true, idempotentHint=true), the description discloses partial-update behavior ('Only what is sent changes; everything left out stays as it is'), default backfill, refusal on plan limits, the exact preview output (preview_url, review_token, text_changes), flow-switch consequences (starts fresh, removes recipients and fields), and dependency (attach_pdf_to_emails needs allow_download).

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

Conciseness3/5

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

The description is a dense, run-on paragraph with long sentences and no clear structure. While most sentences carry useful information, the lack of front-loading and scannability reduces its clarity. It is adequately informative but overly verbose.

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?

Given 15 parameters, no output schema, and a destructive operation, the description is complete: it covers behavior, refusals, output preview, flow switching, and dependencies. Nothing critical for correct invocation is missing.

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 schema already documents all 15 parameters. The description adds some meaning beyond the schema: flow-switch side effects, role behavior on signed_by_sender documents, and the attach_pdf_to_emails dependency. Still, most parameter semantics are left to the 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 description states a specific verb+resource: 'Manages who gets a draft and how it is sent', then enumerates the managed settings. It distinguishes itself from siblings by explicitly excluding field placement (edit_document) and sending (send_document). An agent can tell what it does and what it does not do.

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 explicitly states when to use this tool ('covers any of these changes, such as "make it expire in 7 days"') and when not to ('It places no fields: a signer needs at least one, such as a signature, which edit_document places'). It also names alternatives for related tasks (edit_document for fields, send_document for actual sending).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources