Skip to main content
Glama

signvoy_update_document

Idempotent

Update a draft document before sending. Only allowed while the document is in 'draft' status. Use this to fix recipient names, email addresses, recipient types, the document name, the signing message, the email subject, routing mode, or reminder cadence. Replaces the entire recipients list when provided — include all recipients, not just the ones being changed.

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

Input Schema

NameRequiredDescriptionDefault
nameNoUpdated document title.
messageNoUpdated personal message included in the signing invitation email.
recipientsNoReplacement recipients list. When provided, replaces all recipients. Include every recipient, not just the changed ones.
document_idYesDraft document UUID to update.
expiry_daysNoDays after sending that the document can still be signed. The countdown starts when the document is sent.
routing_modeNoSigning-order mode. parallel: all recipients sign at once. sequential: recipients sign group-by-group in ascending order.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare idempotentHint and destructiveHint=false; the description adds the draft-gating constraint and, critically, that the recipients array is a full replacement requiring every recipient to be re-listed — a non-obvious behavior that would otherwise cause silent data loss. It does not describe what the response looks like, but no output schema exists and annotations already cover the safety profile.

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?

Three sentences, front-loaded with the action and its precondition, then the field list, then the one dangerous gotcha. Nothing is repeated for padding and the replacement warning is placed last for emphasis.

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 an 8-parameter mutation with no output schema, the description covers the operating constraint, the editable surface, and the replacement hazard. Minor gaps remain — it does not state whether updating is partial/merge for the scalar fields, nor what a successful update returns — but the rich schema descriptions absorb most of that burden.

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% and the per-field descriptions (routing_mode, expiry_days, order, roleKey, workspace_id fallback) are detailed, so the description only needs to point at the field set. It does that in a single enumeration without adding format or ordering semantics beyond the schema, which is the correct baseline for full coverage.

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 ("Update a draft document") and bounds it in time ("before sending"), which cleanly separates it from signvoy_send_document and signvoy_create_document. The follow-on sentence enumerates the mutable fields, so an agent knows the tool's surface without opening 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 Guidelines4/5

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

Gives a hard precondition — only allowed while the document is in 'draft' status — plus a plain-language list of the fixes this tool is meant for. It stops short of naming alternatives (e.g., that already-sent documents require void/remind paths), so it is clear context without explicit exclusion routing.

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