Skip to main content
Glama

signvoy_create_document

Create a new signing document (in 'draft' state) from a published template. PREREQUISITE: call signvoy_get_template first to retrieve the recipient role keys — each entry in 'recipients' must match a roleKey from the template. Call signvoy_send_document afterwards to email recipients. Keep create and send separate so a human can review the draft before real emails go to counterparties.

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": {
      "template_id": "<template_id>",
      "recipients": "<recipients>"
    },
    "name": "signvoy_create_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoDocument title. Defaults to the template name.
messageNoOptional personal message included in the signing invitation email.
recipientsYesEveryone involved, in signing order. One entry per template recipient role, plus any 'cc' or 'viewer' entries. At least one must sign or view.
expiry_daysNoDays after sending that the document can still be signed. Defaults to the template's deadline. The countdown starts when the document is sent, not when it is created.
template_idYesPublished template UUID. Get from signvoy_list_templates (hasPublishedVersion must be true).
workspace_idNoTarget workspace UUID. Safe to omit only when the user belongs to exactly one workspace; required otherwise, and omitting it then fails with the list of candidates. Call signvoy_list_workspaces to find it.
email_subjectNoReplaces the generated subject line on the signing request and reminders. Completion, decline and cancellation notices always keep their standard wording. Omit to use the generated subject.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations (idempotentHint=false, destructiveHint=false), the description discloses the resulting state ('draft'), the fact that no emails go out at creation, and the review checkpoint before counterparties are contacted. It stops short of covering failure modes or permission requirements, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the outcome, then prerequisites, then the follow-up and the reason for the split. No sentence is padding, and the ordering mirrors the agent's actual decision sequence.

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?

For a 7-parameter creation tool with fully documented schema and no output schema, the description supplies the missing workflow context: prerequisite lookup, downstream send, and the draft-state safety property. Nothing an agent needs to call it correctly in sequence is absent.

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 baseline is 3; the description still adds real meaning by explaining that each 'recipients' entry must match a roleKey from the template and by tying the recipient list to a prior signvoy_get_template call. It adds cross-field relational context the schema does not encode.

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 plus two distinguishing qualifiers: the document is created 'in draft state' and 'from a published template'. That separates it cleanly from siblings like signvoy_send_document and signvoy_update_document without requiring the schema.

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?

Gives explicit ordering rules: call signvoy_get_template first to obtain role keys, call signvoy_send_document afterwards to email recipients. It also states the design rationale (keep create and send separate so a human reviews the draft), which tells the agent not to try to accomplish both in one call.

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