Skip to main content
Glama
Synctest-hub

BoldSign MCP Server

revoke_document

Cancel an in-progress document signing process to prevent signers from viewing or signing it. Provide a document ID and reason to revoke access.

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

  • Core handler function that initializes the BoldSign DocumentApi, constructs the RevokeDocument request from input payload, calls the revokeDocument API method, handles the response, and catches errors using utility functions.
    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 for the revoke_document tool, validating documentId (required), message (string), and optional onBehalfOf (email).
    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 object registering the 'revoke_document' tool (method name), description, input schema, and wrapper handler delegating to the core revokeDocumentHandler.
    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);
      },
    };
  • Inclusion of revokeDocumentToolDefinition in the array of documents API tool definitions, which is later aggregated in src/tools/index.ts.
    export const documentsApiToolsDefinitions: BoldSignTool[] = [
      getDocumentPropertiesToolDefinition,
      listDocumentsToolDefinition,
      listTeamDocumentsToolDefinition,
      sendReminderForDocumentToolDefinition,
      revokeDocumentToolDefinition,
    ];
  • Aggregation of all BoldSign tools including documentsApiToolsDefinitions (containing revoke_document) into the main definitions array used for MCP tool registration.
    export const definitions: BoldSignTool[] = [
      ...contactsApiToolsDefinitions,
      ...documentsApiToolsDefinitions,
      ...templatesApiToolsDefinitions,
      ...usersApiToolsDefinitions,
      ...teamsApiToolsDefinitions,
    ];
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 precondition ('in-progress status documents'), and the actor requirement ('sender of the document'). It doesn't mention error conditions or response format, but covers the essential behavioral traits.

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 perfectly front-loaded and efficient. The first sentence establishes the core action, the second explains the consequence, and the third specifies the precondition. Every sentence earns its place with zero wasted words.

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 does well by explaining the irreversible effect, actor requirements, and document status precondition. It could be more complete by mentioning error scenarios or response format, but covers the critical context given the tool's complexity.

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, maintaining the baseline score of 3 for adequate but not enhanced parameter semantics.

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 specific action ('revoke'), resource ('document'), and scope ('signing process'). It distinguishes this tool from sibling tools like 'list_documents' or 'send_document_from_template' by focusing on termination rather than creation or retrieval.

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 for when to use this tool ('on the in-progress status documents') and the role requirement ('by the sender of the document'). However, it doesn't explicitly mention when NOT to use it or name specific alternatives for related actions.

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

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