Skip to main content
Glama

Docflare

Send a document

send_document
Destructive

Sends a prepared document to its recipients. This cannot be undone. It takes the review_token of the latest preview, from prepare_document or edit_document, once the user has confirmed that preview, and the email of every signer and CC that preview lists, and sends exactly what it showed. A document the user signs themselves (signed_by_sender) is signed with the user's signature as the preview shows it and goes to its recipients at once as the signed copy. It refuses when those emails are not exactly the document's recipients, when the document changed since, naming what changed, or when the preview is older than 10 minutes. When a send fails or gets no answer, try the same review_token again: it stays valid until a send goes through, and a document is never sent twice. With link delivery, the answer gives each signer's signing link to share. When everyone has signed, Docflare emails the user, and document_status shows the progress.

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>",
      "review_token": "<review_token>",
      "recipients": "<recipients>"
    },
    "name": "send_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe document id.
recipientsYesThe email of every signer and CC in that preview, or of everyone who gets the signed copy.
review_tokenYesThe review_token from the latest prepare_document or edit_document answer, after the user confirmed its preview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses irreversibility, the exact-match recipient rule, the 10-minute preview expiry, idempotency ('never sent twice'), link-delivery return behavior, and the email notification on completion. For a destructive, open-world mutation this is unusually rich context.

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?

Front-loads the critical 'cannot be undone' warning and wastes few words, but the middle run-on clause about recipients and signed_by_sender is dense and harder to parse than it needs to be.

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?

Covers the destructive nature, preconditions, failure and retry semantics, return behavior, and post-send notification and status tracking. Nothing an agent needs to invoke this correctly is missing, even without an output schema.

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 already 100%, yet the description adds real meaning: review_token must be from the latest preview and after user confirmation, and recipients must be exactly the preview's signers and CC or the send is refused. It also introduces the signed_by_sender case, which the schema does not mention.

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?

States a specific verb and resource ('Sends a prepared document to its recipients') and locates itself in the workflow by naming prepare_document and edit_document as the source of the review_token. An agent can distinguish it from those siblings without opening their schemas.

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?

Explicitly says to send only after the user has confirmed the latest preview, names the three refusal conditions, and tells the agent to retry with the same review_token on failure or timeout. Both when-to-use and when-not-to-use are covered.

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