Skip to main content
Glama

signvoy_create_signing_link

Idempotent

Generate a short-lived embedded signing URL for a specific recipient of a sent document. The recipient can sign without logging in. Only available for sent documents with pending recipients. Default TTL is 1 h.

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>",
      "document_recipient_id": "<document_recipient_id>"
    },
    "name": "signvoy_create_signing_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesDocument UUID. Must be in 'sent' or 'in_progress' 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.
expires_in_secondsNoTTL in seconds (60–86400). Default: 3600.
document_recipient_idYesRecipient UUID from signvoy_get_document_status recipients[].id. Recipient must still be in 'pending' status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations supply idempotentHint=true and destructiveHint=false, so safety/mutability is partly covered, and the description adds useful context: the link is short-lived, the recipient can sign without logging in, and there is a 1 h default TTL. However, it does not say whether generation invalidates prior links, whether the URL is single-use, or whether special permissions are required — meaningful gaps for a credential-issuing tool.

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, each load-bearing: verb+resource first, then login-free behavior, then eligibility, then the TTL default. No redundant restatement of the tool name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no readOnlyHint, the definition should explain what comes back (a URL plus expiry) and how the token is scoped; it does not. Eligibility and TTL are covered well, but for a tool that mints an access-granting URL the return contract is left implicit.

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 the schema already documents all four parameters, including workspace_id fallback behavior and recipient lookup path. The description only restates the TTL default and the recipient-pending precondition, adding little meaning beyond the schema. Baseline 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 ('Generate') and resource ('short-lived embedded signing URL'), scoped to 'a specific recipient of a sent document'. This is clearly distinguishable from sibling tools like signvoy_get_signed_pdf_url (retrieves a PDF) or signvoy_send_document (initiates sending).

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 concrete eligibility gate: 'Only available for sent documents with pending recipients,' which tells the agent when the call will succeed and when it will not. It stops short of naming an alternative to use when the document is not yet sent (e.g., send_document), so it is not a full routing rule.

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