Skip to main content
Glama

Cancel signing invite

cancel_invite
DestructiveIdempotent

Cancel all active pending signing invites on a document or document group. Provide the entity ID and an optional reason for cancellation.

Instructions

Cancel all active (pending) signing invites on a document or document group. The entity's state may have changed in the SignNow editor since you last looked — re-read the current state first to confirm the current invite state, not what you saw earlier in the conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoOptional reason for cancellation
entity_idYesID of the document or document group
entity_typeNoType of entity: 'document' or 'document_group' (optional). Auto-detected if not provided (tries document_group first). Pass explicitly to save one API call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesResult status: 'cancelled' (invites were cancelled), 'invite_not_sent' (no active invite found), 'completed' (all signers already completed)
entity_idYesDocument or document group ID
entity_typeYesEntity type: 'document' or 'document_group'
cancelled_invite_idsNoList of cancelled invite IDs (empty when status is not 'cancelled')
cancelled_invite_typeNoType of cancelled invites: 'field', 'freeform', or 'embedded' (populated only when status is 'cancelled')
Behavior4/5

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

Annotations indicate destructive hint and idempotent hint. The description adds that all active invites are cancelled and warns about state changes, providing behavioral context beyond annotations.

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?

The description is two sentences: first states the action, second provides a crucial caution. No redundant information, efficiently conveyed.

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?

The description covers the tool's purpose, scope (document/group), and a practical caution about state staleness. Output schema exists, so return values are covered. Could potentially mention idempotency, but annotations already provide that.

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 parameters. The description does not add further parameter semantics, maintaining the baseline score.

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 cancels active signing invites on a document or document group. The verb 'cancel' and resource 'signing invites' are specific, and the tool is distinct from sibling tools like send_invite or get_invite_status.

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 advises to re-read the current state before cancelling, implying when to use this tool cautiously. It provides context about potential stale state but does not explicitly list when not to use or alternatives.

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