Skip to main content
Glama

Create a draft document

create_draft

Save markdown as a draft document. Recipients are detected from the signature fields. Drafts are free and can be updated any number of times. Set send=true to send immediately (uses one envelope). Returns preview_url, a 7-day link to show your human the document and compare styles.

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": {
      "markdown": "<markdown>"
    },
    "name": "create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
sendNoSend for signature immediately after saving.
styleNoVisual style; defaults to the markdown directive or classic.
titleNoOptional title; defaults to the first "# Heading".
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.
messageNoShort personal note from the sender, included in the email.
markdownYesThe full markdown contract with [[signature: First Last <email>]] fields.
metadataNoYour own key/value details for this document, e.g. {"customer_number": "C-1001", "job_number": "J-77", "quote_number": "Q-310"}. Flat object, up to 20 keys (starting with a letter or _, then letters, numbers, _ or -), text or number values up to 500 characters, stored as text. Returned in responses and webhooks; find documents by it with list_documents metadata.
sender_roleNoOptional role shown on the sender's signature, e.g. "Client" or "Director". Used with sender_signs=true.
sender_signsNotrue adds a signature field for the sender (the account holder, using their name and email); false removes it. Only for two-sided agreements (services/contractor agreements, mutual NDAs, leases, partnerships). Never for quotes, proposals, consents, acknowledgements, waivers or one-way NDAs, where only the recipient signs. Check validation.signing_advice and ask the human if unsure.
verify_signersNoTeam plans: true makes every signer confirm a one-time code emailed to them before their signature is recorded (adds <!-- md2sign:verify=email -->); false turns it off for this document even when the account verifies signers by default (verify=none). Omit to use the account default.
external_referenceNoYour own ID for this document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / metadata
      Added value: +{
      +  "description": "Your own key/value details for this document, e.g. {\"customer_number\": \"C-1001\", \"job_number\": \"J-77\", \"quote_number\": \"Q-310\"}. Flat object, up to 20 keys (starting with a letter or _, then letters, numbers, _ or -), text or number values up to 500 characters, stored as text. Returned in responses and webhooks; find documents by it with list_documents metadata.",
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / verify_signers / description
      Previous value: -"Pro: true makes every signer confirm a one-time code emailed to them before their signature is recorded (adds <!-- md2sign:verify=email -->); false turns it off for this document even when the account verifies signers by default (verify=none). Omit to use the account default."New value: +"Team plans: true makes every signer confirm a one-time code emailed to them before their signature is recorded (adds <!-- md2sign:verify=email -->); false turns it off for this document even when the account verifies signers by default (verify=none). Omit to use the account default."
  3. 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."
  4. Changed1 schema field changed
    • addedInput schema / properties / verify_signers
      Added value: +{
      +  "description": "Pro: true makes every signer confirm a one-time code emailed to them before their signature is recorded (adds <!-- md2sign:verify=email -->); false turns it off for this document even when the account verifies signers by default (verify=none). Omit to use the account default.",
      +  "type": "boolean"
      +}
  5. Changed2 schema fields changed
    • addedInput schema / properties / sender_role
      Added value: +{
      +  "description": "Optional role shown on the sender's signature, e.g. \"Client\" or \"Director\". Used with sender_signs=true.",
      +  "type": "string"
      +}
    • addedInput schema / properties / sender_signs
      Added value: +{
      +  "description": "true adds a signature field for the sender (the account holder, using their name and email); false removes it. Only for two-sided agreements (services/contractor agreements, mutual NDAs, leases, partnerships). Never for quotes, proposals, consents, acknowledgements, waivers or one-way NDAs, where only the recipient signs. Check validation.signing_advice and ask the human if unsure.",
      +  "type": "boolean"
      +}
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already cover read-only, destructive, idempotent, and open-world hints. The description adds useful behavioral context: recipients come from signature fields, drafts are free and repeatedly updatable, send=true consumes one envelope, and a 7-day preview_url is returned.

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, tightly scoped, and contains no filler. Each sentence adds practical information: purpose, recipient detection, draft economics, send behavior, and preview return value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 11-parameter tool with a fully documented schema and no output schema, the description covers the key workflow and return preview_url. It does not mention validation guidance or sibling routing, but the core behavior an agent needs is present.

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 description coverage is 100%, so the schema already carries most parameter meaning. The description still adds useful detail by explaining that recipients are inferred from the markdown signature fields and that send=true uses one envelope.

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?

The description states a specific verb and resource: save markdown as a draft document. It also clarifies the optional immediate-send behavior and recipient detection, but it does not explicitly distinguish the tool from siblings such as update_draft, send_document, or create_document_from_template.

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

Usage Guidelines4/5

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

It gives clear context for choosing between drafting and sending immediately via send=true, and explains that drafts are free and iterable. It does not name alternatives or state when not to use this tool, leaving sibling routing to inference.

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.