Skip to main content
Glama
Synctest-hub

BoldSign MCP Server

get_template_properties

Retrieve detailed properties and settings for a specific BoldSign e-signature template using its unique template ID.

Instructions

Retrieves the detailed properties and settings of a specific BoldSign template using its unique template ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateIdYesRequired. The unique identifier (ID) of the template to retrieve. This can be obtained from the list templates tool.

Implementation Reference

  • The main handler function that executes the tool logic: creates TemplateApi, sets config, calls getProperties API, handles response/error.
    async function getTemplatePropertiesHandler(payload: GetTemplatePropertiesSchemaType): Promise<McpResponse> {
      try {
        const templateApi = new TemplateApi();
        templateApi.basePath = configuration.getBasePath();
        templateApi.setApiKey(configuration.getApiKey());
        const templateProperties: TemplateProperties = await templateApi.getProperties(payload.templateId);
        return handleMcpResponse({
          data: templateProperties,
        });
      } catch (error: any) {
        return handleMcpError(error);
      }
    }
  • Zod input schema validating the required templateId parameter.
    const GetTemplatePropertiesSchema = z.object({
      templateId: commonSchema.InputIdSchema.describe(
        'Required. The unique identifier (ID) of the template to retrieve. This can be obtained from the list templates tool.',
      ),
    });
  • Tool definition registering the tool with MCP: specifies method name, description, input schema, and delegates to the handler.
    export const getTemplatePropertiesToolDefinition: BoldSignTool = {
      method: ToolNames.GetTemplateProperties.toString(),
      name: 'Get template properties',
      description:
        'Retrieves the detailed properties and settings of a specific BoldSign template using its unique template ID.',
      inputSchema: GetTemplatePropertiesSchema,
      async handler(args: unknown): Promise<McpResponse> {
        return await getTemplatePropertiesHandler(args as GetTemplatePropertiesSchemaType);
      },
    };
  • Registration in templates tools array, which is later included in main tools.
    export const templatesApiToolsDefinitions: BoldSignTool[] = [
      sendDocumentFromTemplateDynamicToolDefinition,
      listTemplatesToolDefinition,
      getTemplatePropertiesToolDefinition,
    ];
  • Enum value defining the tool's string identifier.
    GetTemplateProperties = 'get_template_properties',
Behavior2/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 of behavioral disclosure. It states the tool retrieves details but does not mention whether it's read-only, requires authentication, has rate limits, or what the return format looks like. For a tool with no annotation coverage, this leaves significant behavioral traits undisclosed, though it doesn't contradict any annotations.

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 a single, well-structured sentence that efficiently conveys the tool's purpose and key usage note. It is front-loaded with the main action and resource, with no wasted words, making it highly concise and easy to parse.

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 low complexity (one parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and parameter source but lacks details on behavioral aspects like authentication or return format. For a simple retrieval tool, this is minimally viable but leaves gaps in contextual understanding.

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 description adds minimal meaning beyond the input schema, which has 100% coverage for the single parameter 'templateId'. It mentions the ID is 'unique' and can be obtained from another tool, but this is already implied in the schema's description. With high schema coverage, the baseline is 3, as the description doesn't significantly enhance parameter understanding.

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 ('Retrieves') and resource ('detailed properties and settings of a specific BoldSign template'), making the purpose evident. It distinguishes from siblings like 'list_templates' by focusing on a single template's details rather than listing multiple. However, it doesn't explicitly contrast with 'get_document_properties' or 'get_contact', leaving some sibling differentiation incomplete.

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 mentioning the template ID can be obtained from 'list templates tool', suggesting a workflow. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_document_properties' or 'list_templates', and does not specify prerequisites or exclusions, leaving usage context somewhat vague.

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