Skip to main content
Glama

signvoy_send_document

Idempotent

Send a draft document to its recipients. Emails each recipient with a personalised signing link. Real emails will be sent to real counterparties — confirm with the user before calling. Idempotent: calling on an already-sent document is a no-op.

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_send_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesDocument UUID to send. Must be in 'draft' status.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false; the description earns credit by making the external side effect explicit — real emails reach real counterparties — and by stating the concrete consequence of idempotency (calling on an already-sent document is a no-op). It does not say what happens on partial failure or whether the document's status changes, so it stops short of full disclosure.

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 action and then escalating to the safety warning and idempotency behavior. Every sentence carries distinct information; nothing repeats the title or schema.

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 two-parameter mutation with full schema coverage and no output schema, the description covers the essentials: what it does, the irreversible external side effect, and re-call safety. The only gap is what an agent should expect afterward, such as whether the document transitions out of draft or what reminder/follow-up path applies.

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%, so both document_id (UUID, must be 'draft') and workspace_id (with the single-workspace omission rule and pointer to signvoy_list_workspaces) are already fully documented. The description's mention of 'draft document' merely echoes the schema and adds no format, sourcing, or edge-case detail beyond it.

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 opens with a specific verb+resource pair ('Send a draft document to its recipients') and elaborates that each recipient receives a personalised signing link. That is unambiguous against read-only siblings like signvoy_get_document_status or signvoy_get_audit_trail, though no sibling is explicitly named as an alternative.

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 a clear precondition ('draft document') and an explicit confirmation requirement ('confirm with the user before calling') because real emails go out. It does not mention what to do once a document is already sent (e.g., whether signvoy_remind_document is the appropriate next step), but the idempotency note covers the immediate re-call case.

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