Skip to main content
Glama

revoke_document

Cancel an in-progress document to prevent signers from viewing or completing it. Provide the document ID and reason for revocation.

Instructions

The document signing process can be called off or revoked by the sender of the document. Once you revoke a document, signers can no longer view or sign it. Revoke action can only be performed on the in-progress status documents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdYesRequired. The unique identifier (ID) of the document to revoke. This can be obtained from the list documents tool.
messageYesThe exact reason for performing a revoke action.
onBehalfOfNoOptional. Email address of the sender when creating a document on their behalf. This email can be retrieved from the `behalfOf` property in the get document or list documents tool.

Implementation Reference

  • The main handler function that implements the logic for the 'revoke_document' tool by calling the BoldSign DocumentApi.revokeDocument method.
    async function revokeDocumentHandler(payload: RevokeDocumentSchemaType): Promise<McpResponse> {
      try {
        const documentApi = new DocumentApi();
        documentApi.basePath = configuration.getBasePath();
        documentApi.setApiKey(configuration.getApiKey());
        const revokeDocumentRequest: RevokeDocument = new RevokeDocument();
        revokeDocumentRequest.message = payload.message;
        revokeDocumentRequest.onBehalfOf = payload.onBehalfOf;
        const documentResponse: returnTypeI = await documentApi.revokeDocument(
          payload.documentId,
          revokeDocumentRequest,
        );
        return handleMcpResponse({
          data: documentResponse?.response?.data ?? documentResponse,
        });
      } catch (error: any) {
        return handleMcpError(error);
      }
    }
  • Zod input schema defining parameters for the revoke_document tool: documentId, message, and optional onBehalfOf.
    const RevokeDocumentSchema = z.object({
      documentId: commonSchema.InputIdSchema.describe(
        'Required. The unique identifier (ID) of the document to revoke. This can be obtained from the list documents tool.',
      ),
      message: z.string().describe('The exact reason for performing a revoke action.'),
      onBehalfOf: commonSchema.EmailSchema.optional()
        .nullable()
        .describe(
          'Optional. Email address of the sender when creating a document on their behalf. This email can be retrieved from the `behalfOf` property in the get document or list documents tool.',
        ),
    });
  • Tool definition that registers the 'revoke_document' tool, specifying its method name, description, input schema, and wrapper handler.
    export const revokeDocumentToolDefinition: BoldSignTool = {
      method: ToolNames.RevokeDocument.toString(),
      name: 'Revoke document',
      description:
        'The document signing process can be called off or revoked by the sender of the document. Once you revoke a document, signers can no longer view or sign it. Revoke action can only be performed on the in-progress status documents.',
      inputSchema: RevokeDocumentSchema,
      async handler(args: unknown): Promise<McpResponse> {
        return await revokeDocumentHandler(args as RevokeDocumentSchemaType);
      },
    };
  • Aggregation of document-related tools including revokeDocumentToolDefinition for higher-level registration.
    export const documentsApiToolsDefinitions: BoldSignTool[] = [
      getDocumentPropertiesToolDefinition,
      listDocumentsToolDefinition,
      listTeamDocumentsToolDefinition,
      sendReminderForDocumentToolDefinition,
      revokeDocumentToolDefinition,
    ];
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the irreversible consequence ('signers can no longer view or sign it'), the actor requirement ('by the sender'), and the state constraint ('in-progress status documents'). This covers key behavioral aspects for a destructive operation.

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 efficiently structured in three sentences that each add distinct value: purpose statement, consequence disclosure, and usage constraint. There's no wasted language, and the most critical information (what the tool does) is presented first.

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 destructive operation with no annotations and no output schema, the description provides good coverage of the essential context: what it does, who can do it, when it applies, and the irreversible effect. It could potentially mention authentication requirements or error conditions, but overall it's quite complete for its complexity level.

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 three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, which is acceptable given the comprehensive schema coverage. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 action ('revoke'), resource ('document'), and scope ('signing process'). It specifies that only the sender can perform this action, distinguishing it from other document-related tools like list_documents or send_reminder_for_document_sign which have different purposes.

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 provides clear context about when to use this tool: 'Revoke action can only be performed on the in-progress status documents.' It doesn't explicitly mention when NOT to use it or name specific alternatives, but the status restriction provides meaningful guidance for appropriate usage.

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/boldsign/boldsign-mcp'

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