Signvoy logoSignvoy

MCP Prompts

Prompt library

Prompts that work reliably against the Signvoy MCP server, grouped by what you are trying to get done. Each group notes why the phrasing matters — most failed signing workflows are prompt problems, not tool problems.

Copy-paste ready
Client-agnostic

Built-in prompts

The server ships 2 named prompts of its own. These are not text you type — they are workflows the client can load, so the model gets the correct tool ordering and guardrails without you having to describe them. In Claude Code, list them with /mcp; other clients expose them in a prompt or slash-command picker.

signvoy_send_for_signature

Send a document for e-signature

Six-step workflow from picking a template through to sending, with a mandatory human review before any email goes out.

  1. signvoy_list_workspaces — always first. If several come back, ask the user which one and pass its workspace_id to every later call.
  2. signvoy_list_templates — list published templates (hasPublishedVersion=true).
  3. signvoy_get_template — fetch the chosen template's recipient role keys.
  4. signvoy_create_document — create the draft, one entry per roleKey with name and email.
  5. Review with the user — share review_url and the recipient list. If send_blockers is non-empty, call signvoy_update_document first.
  6. signvoy_send_document — send only after explicit user confirmation.
signvoy_check_signing_status

Check signing status and follow up

Four-step workflow for finding a pending document, seeing who has signed, nudging stragglers, and downloading the result.

  1. signvoy_list_documents — filter by status sent or in_progress.
  2. signvoy_get_document_status — per-recipient state: pending, signed, or declined.
  3. signvoy_remind_document — only if the user wants to nudge, and only once.
  4. signvoy_get_signed_pdf_url — once completed. Request fresh; do not cache.

Sending for signature

The pattern that works: name the template exactly, give complete recipient details, and ask for the review link before sending. That last clause is what keeps drafting and sending as two separate, human-gated steps.

prompts
# Single recipient, review first
Draft an NDA from my "Mutual NDA" template for Dana Kim at dana@example.com.
Show me the review link and recipient list before sending anything.

# Multi-role template
Create a document from my "Consulting Agreement" template. The client signer
is Priya Raman (priya@acme.com) and our countersigner is me. List the
template's roles first so you map each person to the right one.

# Sequential signing
Create an offer letter from my "Offer Letter" template for Sam Ortiz
(sam@example.com), with our VP signing first and Sam second. Set routing to
sequential.

# Fix a draft before sending
The email on that draft is wrong — it should be dana.kim@example.com.
Update the draft and show me the corrected recipient list.

# Send, once you're satisfied
That looks right. Send it.
Ask it to list templates first when you are not certain of the exact name. Only templates with a published version can create documents, and a loose description can lead the assistant to a draft-only template with a similar name.

Tracking and chasing

This is where an agent genuinely beats the dashboard: it can read across many documents and summarise who is blocking what, which otherwise means clicking through each one.

prompts
# The daily standup question
Which of my Signvoy documents are still waiting on signatures, and for each
one, who hasn't signed yet?

# Find the stale ones
List documents in sent or in_progress status, oldest first, and tell me which
have been outstanding longest.

# Selective reminders
For the documents that have been pending more than a week, show me the list
and ask me which ones to remind before sending anything.

# Single document detail
What's the status of the Acme MSA? Show me each recipient and whether they've
signed, declined, or are still pending.

# Collect the result
The Acme MSA is complete — get me the download link for the signed PDF.
Reminders are per document, not per recipient: signvoy_remind_document emails every pending recipient on that document. Ask for the list and approve selectively rather than saying “remind everyone”.

Audit and compliance

The audit trail is append-only and records actor, IP address, and timestamp for every event. Asking an assistant to read it is faster than reconstructing a timeline by hand.

prompts
# Reconstruct a timeline
Show me the audit trail for the Acme MSA and summarise it as a timeline:
who did what, when, and from which IP.

# Verify a disputed signature
A counterparty says they never received the Acme MSA. Check the audit trail
for send and view events for their email address.

# Separate agent activity from human activity
In the audit trail for document <id>, which events were performed through MCP
rather than in the dashboard?

That last one works because mutating MCP calls tag their audit events actorSource: "mcp".

Embedded signing

Useful mainly while building or debugging an embedded signing integration — the assistant can mint a real link for you to load.

prompts
# Get a link to test your embed
Create a signing link for the pending recipient on document <id> so I can
load it in my local embed.

# Find the right recipient id first
Show me the recipients on document <id> with their ids, then create a signing
link for the one that's still pending.
The returned URL grants signing access with no login. Treat it as a secret — do not paste it into shared channels or commit it. Note also that the document must be in status exactly sent; once anyone signs and it moves to in_progress, link creation fails.

Writing reliable prompts

Be specific about identity

Names alone are ambiguous; emails are not. A recipient created without an email produces a RECIPIENT_EMAIL_MISSING send blocker and the document cannot be sent until it is fixed.

Say “show me” before “send”

Asking for the review link is what reliably stops a capable model from chaining create and send in one turn. The server enforces the split at the tool level, but the prompt is what stops the model from immediately calling both.

Name the workspace when you have several

With more than one workspace on your account, omitting workspace_idfails rather than picking one, costing you a turn. Say “in my Acme workspace” up front and let the assistant resolve it via signvoy_list_workspaces.

Prefer questions over instructions for status

“Which documents are pending?” keeps the assistant in read-only tools. “Chase everyone who hasn't signed” invites it to start sending email. Ask, review, then instruct.

FAQ

What should I ask an AI assistant to send a contract?

Name the template, the recipient, and their email, and ask to see the review link before anything is sent. For example: draft an NDA from my Mutual NDA template for Dana Kim at dana@example.com and show me the review link first. The explicit review request keeps the draft and send steps separate.

Why does naming the template exactly matter?

Documents can only be created from templates with a published version. If you describe a template loosely, the assistant may pick a similarly named draft-only template and the create call will fail. Asking it to list templates first avoids the guess.

What are MCP prompts, as opposed to just typing a request?

MCP prompts are named workflows the server itself provides to the client. Signvoy registers two — signvoy_send_for_signature and signvoy_check_signing_status — which the assistant can load to get the correct tool ordering and the mandatory human-review step, rather than inferring the sequence.

Can I ask an AI assistant to remind everyone who hasn't signed?

Yes, and it is one of the highest-value prompts. Ask which documents are still waiting and who is holding each one up, then approve reminders selectively. Signvoy's remind tool sends to all pending recipients on a document at once, so review the list before approving.

Hören Sie auf, Unterschriften hinterherzurennen

Schließen Sie sich Tausenden von Teams an, die Signvoy nutzen, um Deals abzuschließen, Kunden zu gewinnen und Verträge zu unterzeichnen — schneller.

Kostenloses Konto erstellen
Anmelden

Keine Kreditkarte · Dauerhaft kostenloser Plan · Jederzeit kündbar