Skip to main content
Glama

Send for e-signature with md2sign

send_for_signature

Get a document e-signed instead of printed. Nothing is sent to anyone: this hands the markdown to md2sign (same company) and returns a link your human opens to sign up or log in, where the document waits as a draft ready to send. The link works once and expires after 24 hours; md2sign keeps the document until then. Also returns how to connect md2sign's own MCP server so you can send it directly. Use when the document has signature lines and your human wants it signed.

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": "send_for_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
markdownYesThe full markdown document, with a [[signature: Name <email>]] line for each signer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: clarifies that no email is sent to anyone, that the work product is a draft awaiting the human, that the link is single-use and expires in 24 hours, and that md2sign retains the document until then. That single-use/expiry/reversibility detail is exactly what an agent needs for a mutating, open-world call.

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-loaded with the core action, with the privacy clarification and expiry caveat following in order of importance. Some phrasing is dense (parenthetical '(same company)', em-dash asides) and the 'nothing is sent / document waits as a draft' point is made twice, but no sentence is fully 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?

No output schema exists, and the description fully compensates by describing both return values (the sign link and the md2sign MCP connection instructions) plus the lifetime of what is returned. For a one-parameter tool this leaves no significant gap.

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?

Only one parameter and schema coverage is 100%, so the schema already documents the markdown field and its [[signature: Name <email>]] convention. The description adds no further meaning about that parameter (e.g., size limits or multi-signer ordering), so the baseline of 3 applies.

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+resource (get a document e-signed) and immediately names the mechanism (hands the markdown to md2sign and returns a link). That mechanism description clearly separates it from siblings like render_pdf or validate_markdown without needing 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 Guidelines4/5

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

Explicit trigger condition at the end: 'Use when the document has signature lines and your human wants it signed.' It also implies the alternative path (md2sign's own MCP server, returned in the response) but gives no explicit when-not or comparison to sibling tools.

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.