Skip to main content
Glama

Send a document for signature

send_document
Destructive

Send a draft for signature. Each recipient gets an email from " via md2sign" with the document and a unique signing link. Uses one envelope, however many people sign. Needs a confirmed email and a plan (or its free trial); once sent, the document can't be edited. Returns sending_suspended if recipients reported the account's emails as spam, recipient_opted_out for recipients who asked not to be emailed, quota_exceeded when the envelopes on the plan are used up (with top_up_url to buy more), and trial_limit when a free-trial limit is reached.

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": {
      "document_id": "<document_id>"
    },
    "name": "send_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoAn md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an "Authorization: Bearer <api_key>" header.
messageNoOptional short note from the sender to include in the email.
document_idYesThe document ID returned by create_draft, list_documents or create_document_from_template. Must be a draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your md2sign API key. Only needed if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."New value: +"An md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."
  2. Changed1 schema field changed
    • addedInput schema / properties / document_id / description
      Added value: +"The document ID returned by create_draft, list_documents or create_document_from_template. Must be a draft."
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety bar is low, yet the description adds substantial context: recipients get a unique signing link in an email from "<Company> via md2sign", one envelope covers all signers, and the document becomes immutable after sending. It also enumerates concrete failure modes (sending_suspended, recipient_opted_out, quota_exceeded with top_up_url, trial_limit), which lets the agent interpret errors without extra lookups.

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 action and recipient-facing behavior are front-loaded in the first two sentences, followed by prerequisites, the immutability caveat, and error codes. The error-code sentence is long and dense but each item conveys a distinct recoverable condition, so little is wasted.

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?

With only three parameters, no output schema, and annotations covering the safety profile, the description supplies everything else an agent needs: prerequisites, delivery mechanics, irreversibility, and named error outcomes. Nothing material is left for the caller to guess.

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?

Schema description coverage is 100%, so document_id, message and api_key are already documented in the schema. The description adds no further parameter meaning, such as whether message is plain text or length-limited, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: "Send a draft for signature." That clearly distinguishes it from draft-manipulation siblings like create_draft or update_draft, though it never names test_send_document, the closest sibling, so the agent must infer the difference from the names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real preconditions (confirmed email, paid plan or trial, document must be a draft) and a hard constraint ("once sent, the document can't be edited"). However, it offers no explicit routing guidance such as when to use test_send_document first or void_document afterwards, so the when-to-use-vs-alternative layer is only implied.

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.