Skip to main content
Glama
Synctest-hub

BoldSign MCP Server

send_reminder_for_document_sign

Send reminder emails to signers for pending document signatures. Specify document ID and recipient emails to prompt action on outstanding signature requests.

Instructions

Send reminder emails to signers for pending document signatures. This API allows users to remind signers about outstanding signature requests by specifying the document ID and recipient email addresses. Multiple signers can receive reminders at once, and custom messages can be included. If sending reminders on behalf of another sender, specify the relevant sender email addresses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdYesRequired. The unique identifier (ID) of the document to send a reminder email to signers for pending signatures.
receiverEmailsNoOptional. One or more signer email addresses to send reminders for pending signatures. If multiple signers are required to sign the document, specify their email addresses. If there is not emails provided, it will send reminder to all pending signers. The signers of a document can be obtained from the document-properties tool, using the documentId.
messageNoOptional. Message to be sent in the reminder email. If not provided, the system will use a default reminder message.
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 implementing the tool logic: initializes BoldSign DocumentApi, builds ReminderMessage from input, calls remindDocument API, handles response and errors.
    async function sendReminderForDocumentSignHandler(
      payload: SendReminderForDocumentSignSchemaType,
    ): Promise<McpResponse> {
      try {
        const documentApi = new DocumentApi();
        documentApi.basePath = configuration.getBasePath();
        documentApi.setApiKey(configuration.getApiKey());
        const reminderMessage: ReminderMessage = new ReminderMessage();
        reminderMessage.message = payload.message ?? undefined;
        reminderMessage.onBehalfOf = payload.onBehalfOf ?? undefined;
        const documentResponse: returnTypeI = await documentApi.remindDocument(
          payload.documentId,
          payload.receiverEmails ?? undefined,
          reminderMessage,
        );
        return handleMcpResponse({
          data: documentResponse?.response?.data ?? documentResponse,
        });
      } catch (error: any) {
        return handleMcpError(error);
      }
    }
  • Zod schema defining the input parameters for the tool: documentId (required), receiverEmails (optional array), message (optional), onBehalfOf (optional).
    const SendReminderForDocumentSignSchema = z.object({
      documentId: commonSchema.InputIdSchema.describe(
        'Required. The unique identifier (ID) of the document to send a reminder email to signers for pending signatures.',
      ),
      receiverEmails: z
        .array(commonSchema.EmailSchema.describe('Email address of the signer.'))
        .optional()
        .nullable()
        .describe(
          'Optional. One or more signer email addresses to send reminders for pending signatures. If multiple signers are required to sign the document, specify their email addresses. If there is not emails provided, it will send reminder to all pending signers. The signers of a document can be obtained from the document-properties tool, using the documentId.',
        ),
      message: commonSchema.OptionalStringSchema.describe(
        'Optional. Message to be sent in the reminder email. If not provided, the system will use a default reminder message.',
      ),
      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 tool with MCP: specifies method name, description, input schema, and wrapper handler calling the core handler.
    export const sendReminderForDocumentToolDefinition: BoldSignTool = {
      method: ToolNames.SendReminderForDocumentSign.toString(),
      name: 'Send reminder for document sign',
      description:
        'Send reminder emails to signers for pending document signatures. This API allows users to remind signers about outstanding signature requests by specifying the document ID and recipient email addresses. Multiple signers can receive reminders at once, and custom messages can be included. If sending reminders on behalf of another sender, specify the relevant sender email addresses.',
      inputSchema: SendReminderForDocumentSignSchema,
      async handler(args: unknown): Promise<McpResponse> {
        return await sendReminderForDocumentSignHandler(args as SendReminderForDocumentSignSchemaType);
      },
    };
  • Registers the sendReminderForDocumentToolDefinition in the array of documents API tools, likely used for overall tool registration.
    export const documentsApiToolsDefinitions: BoldSignTool[] = [
      getDocumentPropertiesToolDefinition,
      listDocumentsToolDefinition,
      listTeamDocumentsToolDefinition,
      sendReminderForDocumentToolDefinition,
      revokeDocumentToolDefinition,
    ];
  • Enum constant defining the exact tool name string used in registration.
    SendReminderForDocumentSign = 'send_reminder_for_document_sign',
Behavior3/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 adequately describes the core action (sending reminder emails) and mentions capabilities like multiple signers and custom messages. However, it doesn't address important behavioral aspects like rate limits, authentication requirements, whether this triggers notifications, or what happens if reminders are sent too frequently.

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 appropriately sized at three sentences, front-loading the core purpose. Each sentence adds value: the first states the purpose, the second explains capabilities, and the third addresses the 'on behalf of' scenario. There's minimal redundancy, though the structure could be slightly more streamlined.

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

Completeness3/5

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

For a 4-parameter mutation tool with no annotations and no output schema, the description provides adequate but not comprehensive coverage. It explains what the tool does and when to use it, but lacks details about return values, error conditions, side effects, or system limitations that would be important for an AI agent to understand the full behavioral context.

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?

With 100% schema description coverage, the input schema already documents all parameters thoroughly. The description mentions 'document ID and recipient email addresses' and 'custom messages can be included', which aligns with but doesn't significantly enhance the schema's parameter documentation. 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 tool's purpose with specific verbs ('send reminder emails') and resources ('to signers for pending document signatures'). It distinguishes itself from sibling tools like 'send_document_from_template' by focusing specifically on reminder functionality rather than initial document sending.

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 ('to remind signers about outstanding signature requests') and mentions that signer information can be obtained from the 'document-properties tool'. However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among the sibling tools.

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