Skip to main content
Glama

cancel_envelope

Cancel a sent digital signature envelope and notify signers. Use this tool to stop the signing process for a specific envelope.

Instructions

Cancel a sent envelope. Signers will be notified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envelopeIdYesEnvelope UUID

Implementation Reference

  • The actual API call implementation for canceling an envelope.
    export function cancelEnvelope(creds, envelopeId) {
      return apiCall('POST', `/api/envelopes/${envelopeId}/cancel`, creds);
    }
  • src/index.js:263-275 (registration)
    Registration of the cancel_envelope tool and its handler logic which calls the API helper.
    server.tool(
      'cancel_envelope',
      'Cancel a sent envelope. Signers will be notified.',
      {
        envelopeId: z.string().describe('Envelope UUID'),
      },
      async ({ envelopeId }) => {
        try {
          const data = await api.cancelEnvelope(creds, envelopeId);
          return result(data);
        } catch (err) {
          return errorResult(err);
        }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states that signers will be notified, which adds some context about side effects, but fails to address critical aspects like permissions required, whether cancellation is reversible, rate limits, or error conditions. This leaves significant gaps for a mutation 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?

The description is extremely concise—two short sentences with zero wasted words. It is front-loaded with the core action and efficiently includes a key behavioral note about signer notification.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on permissions, error handling, return values, and differentiation from sibling tools. The mention of signer notification is helpful but insufficient to cover the complexity of canceling an envelope.

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?

The schema description coverage is 100%, with the parameter 'envelopeId' fully documented as 'Envelope UUID'. The description adds no additional parameter details beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without adding value.

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 clearly states the action ('Cancel') and target resource ('a sent envelope'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'delete_envelope' or 'discard_envelope', which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'delete_envelope' or 'discard_envelope'. It mentions that 'Signers will be notified', which hints at a post-send context but doesn't clarify prerequisites, exclusions, or comparative use cases.

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/davidsimoes/digisign-mcp'

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