Skip to main content
Glama

get_document_properties

Retrieve document details including status, metadata, sender and signer information, form fields, and history from BoldSign by providing the document ID.

Instructions

Retrieve comprehensive details of a document in your BoldSign organization. This API allows authorized users, including senders, signers, team admins, and account admins, to access document properties by specifying the unique document ID. The response includes information such as status, metadata, sender and signer details, form fields, and document history. If an unauthorized user attempts to access the document, an unauthorized response will be returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdYesRequired. The unique identifier (ID) of the document to retrieve. This can be obtained from the list documents tool.

Implementation Reference

  • The core handler function that executes the tool logic by calling the BoldSign DocumentApi to retrieve document properties based on the provided document ID, handles errors, and formats the MCP response.
    async function getDocumentPropertiesHandler(payload: GetDocumentPropertiesSchemaType): Promise<McpResponse> {
      try {
        const documentApi = new DocumentApi();
        documentApi.basePath = configuration.getBasePath();
        documentApi.setApiKey(configuration.getApiKey());
        const documentProperties: DocumentProperties = await documentApi.getProperties(payload.documentId);
        return handleMcpResponse({
          data: documentProperties,
        });
      } catch (error: any) {
        return handleMcpError(error);
      }
    }
  • Zod schema defining the input structure for the tool, requiring a documentId.
    const GetDocumentPropertiesSchema = z.object({
      documentId: commonSchema.InputIdSchema.describe(
        'Required. The unique identifier (ID) of the document to retrieve. This can be obtained from the list documents tool.',
      ),
    });
  • The tool definition object that registers the tool with its method name 'get_document_properties', description, input schema, and a wrapper handler calling the main handler.
    export const getDocumentPropertiesToolDefinition: BoldSignTool = {
      method: ToolNames.GetDocumentProperties.toString(),
      name: 'Get document properties',
      description:
        'Retrieve comprehensive details of a document in your BoldSign organization. This API allows authorized users, including senders, signers, team admins, and account admins, to access document properties by specifying the unique document ID. The response includes information such as status, metadata, sender and signer details, form fields, and document history. If an unauthorized user attempts to access the document, an unauthorized response will be returned.',
      inputSchema: GetDocumentPropertiesSchema,
      async handler(args: unknown): Promise<McpResponse> {
        return await getDocumentPropertiesHandler(args as GetDocumentPropertiesSchemaType);
      },
    };
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses behavioral traits such as authorization requirements ('authorized users...'), access control ('unauthorized response will be returned'), and response content ('information such as status, metadata...'). However, it lacks details on rate limits, pagination, or error handling beyond authorization, leaving some gaps for a read operation.

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 and front-loaded, starting with the core purpose. Each sentence adds value: the first states the action, the second covers authorization and input, the third details response content, and the fourth mentions error handling. There's no wasted text, though it 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?

Given the tool's moderate complexity (single parameter, read operation) and lack of annotations and output schema, the description is somewhat complete but has gaps. It covers purpose, authorization, and response overview, but doesn't detail the full output structure or potential side effects, which could be helpful for an AI agent to understand what to expect.

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 input schema has 100% description coverage, with 'documentId' clearly documented. The description adds minimal value beyond the schema, only reiterating that the ID is 'unique' and can be 'obtained from the list documents tool.' This provides slight context but doesn't significantly enhance parameter understanding, so it meets the baseline for high schema coverage.

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 tool's purpose: 'Retrieve comprehensive details of a document in your BoldSign organization.' It specifies the verb ('retrieve') and resource ('document'), but doesn't explicitly differentiate it from sibling tools like 'list_documents' or 'get_template_properties' beyond mentioning it returns 'document properties' by ID. This makes it clear but not fully sibling-distinctive.

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

Usage Guidelines3/5

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

The description implies usage by stating it's for 'authorized users' and requires a 'unique document ID,' but doesn't explicitly say when to use this tool versus alternatives like 'list_documents' for browsing or 'get_template_properties' for templates. It mentions the ID can be 'obtained from the list documents tool,' which provides some context but no direct when/when-not guidance.

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