Skip to main content
Glama

Send signing invite

send_invite
Destructive

Send signing invitations for documents, document groups, templates, or template groups. Supports field-based and freeform invites, auto-detects document type, and allows self-signing with direct signing links.

Instructions

Send invite to sign a document, document group, template, or template group. Supports both field invites (documents with roles/fields) and freeform invites (documents without fields). Document type is auto-detected — omit 'role' for freeform documents. For templates and template groups, automatically creates a document/group first, then sends the invite. Set self_sign=True (and omit orders) to sign the document yourself — the tool resolves the current user's email and populates SendInviteResponse.link with a direct signing link. The 'link' field is also populated when a freeform recipient's email matches the authenticated user's primary email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_idYesID of the document, document group, template, or template group
ordersNoList of orders with recipients (or a JSON string of the same). Required unless self_sign=True. When self_sign=True, omit orders — the tool fills in the current user as the sole recipient.
preview_was_shownNoThis flag signals that the user has viewed the document preview. Prompt the user to view the document before submitting. If the user says yes, call view_document first, show the result, then call send_invite again with preview_was_shown=True. If the user says no, call send_invite with preview_was_shown=False.
entity_typeNoType of entity: 'document', 'document_group', 'template', or 'template_group' (optional). Auto-detected if not provided.
nameNoOptional name for the new document or document group (used only when entity_type is template or template_group)
self_signNoIf True, the tool resolves the current user's primary email server-side and sends a freeform invite to the user themselves. The response's 'link' field is populated with a direct signing link. Must be combined with an empty/omitted orders. Requires a field-less document or document group — for entities with fields/roles, use create_embedded_sending instead.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
invite_idYesID of the created invite
invite_entityYesType of invite entity: 'document' or 'document_group'
linkNoDirect signing link. Populated only when the sender and recipient resolve to the same email (self_sign=True, or the recipient email equals the authenticated user's primary email). None for normal outbound invites.
created_entity_idNoID of the entity created from template (None when entity was document/document_group)
created_entity_typeNoType of created entity: 'document' or 'document_group' (None when entity was document/document_group)
created_entity_nameNoName of the entity created from template (None when entity was document/document_group)
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it explains auto-detection of document type, auto-creation for templates, self-sign resolution of user email and link population, and the preview_was_shown state machine. This fully compensates for the lack of annotation details and provides a clear picture of side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose sentence followed by specific scenarios. It is somewhat lengthy but justified by the tool's complexity (multiple entity types, two invite modes, self-sign, preview flow). Could be slightly more concise, but it remains readable.

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?

Given the tool's complexity (6 parameters, multiple entity types, two invite modes, self-sign, preview requirement), the description covers all necessary aspects for correct invocation. It explains auto-detection, workflow for self-sign and preview, and notes limitations. An AI agent can reliably use this tool based solely on the description.

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?

Although schema coverage is 100%, the description adds meaningful context for key parameters like orders (explaining field vs freeform), self_sign (clarifying restriction to field-less documents), and preview_was_shown (detailing the interaction flow). It goes beyond the schema's descriptions.

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?

The description clearly states the tool sends signing invites and specifies the supported entity types (document, document group, template, template group). It distinguishes between field and freeform invites and mentions self-sign and auto-creation for templates, providing a comprehensive overview of functionality.

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?

The description gives clear guidance on when to use each parameter (e.g., omit 'role' for freeform, set self_sign=True for self-signing) and includes a workflow for preview_was_shown. However, it does not explicitly contrast with sibling tools like create_embedded_invite or send_invite_from_template, though it does mention create_embedded_sending as an alternative for self_sign on fielded documents.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/signnow/sn-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server