Skip to main content
Glama
Synctest-hub

BoldSign MCP Server

get_user

Retrieve detailed user information from BoldSign using their unique ID to manage e-signature workflows and user data.

Instructions

Retrieves detailed information for a specific BoldSign user based on their unique user ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesRequired. The unique identifier (ID) of the user to retrieve. This can be obtained from the list users tool.

Implementation Reference

  • The core handler function implementing the logic for the 'get_user' tool. It initializes the BoldSign UserApi client with configuration and retrieves user properties by userId.
    async function getUserHandler(payload: GetUserSchemaType): Promise<McpResponse> {
      try {
        const userApi = new UserApi();
        userApi.basePath = configuration.getBasePath();
        userApi.setApiKey(configuration.getApiKey());
        const userProperties: UserProperties = await userApi.getUser(payload.userId);
        return handleMcpResponse({
          data: userProperties,
        });
      } catch (error: any) {
        return handleMcpError(error);
      }
    }
  • Zod input schema validation for the 'get_user' tool, requiring a userId.
    const GetUserSchema = z.object({
      userId: commonSchema.InputIdSchema.describe(
        'Required. The unique identifier (ID) of the user to retrieve. This can be obtained from the list users tool.',
      ),
    });
  • Tool definition object for 'get_user', specifying name, description, schema, and handler wrapper. The method is set to 'get_user' from ToolNames.
    export const getUserToolDefinition: BoldSignTool = {
      method: ToolNames.GetUser.toString(),
      name: 'Get user',
      description: 'Retrieves detailed information for a specific BoldSign user based on their unique user ID.',
      inputSchema: GetUserSchema,
      async handler(args: unknown): Promise<McpResponse> {
        return await getUserHandler(args as GetUserSchemaType);
      },
    };
  • Registration of users API tools array, including the getUserToolDefinition.
    export const usersApiToolsDefinitions: BoldSignTool[] = [getUserToolDefinition, listUsersToolDefinition];
  • Top-level registration of all BoldSign tools, spreading usersApiToolsDefinitions which includes 'get_user'.
    export const definitions: BoldSignTool[] = [
      ...contactsApiToolsDefinitions,
      ...documentsApiToolsDefinitions,
      ...templatesApiToolsDefinitions,
      ...usersApiToolsDefinitions,
      ...teamsApiToolsDefinitions,
    ];
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 that the tool retrieves detailed information, which implies a read-only operation, but does not specify behavioral traits such as authentication requirements, rate limits, error handling, or what 'detailed information' entails. The description adds basic context but lacks depth for a tool without 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 without unnecessary words. It is front-loaded with the core action and resource, making it easy to understand quickly.

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 minimally adequate. It covers the basic purpose but lacks details on output format, error cases, or integration with sibling tools. Without annotations or output schema, more context on behavior would improve completeness, but it meets the minimum for a simple retrieval tool.

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 fully documents the single parameter 'userId'. The description adds no additional meaning beyond what the schema provides (e.g., it does not explain format constraints or examples). With high schema coverage, the baseline score of 3 is appropriate as the description does not compensate but also does not detract.

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 verb ('Retrieves') and resource ('detailed information for a specific BoldSign user'), making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'list_users' beyond the 'specific' qualifier, which is implied but not stated as a distinction.

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 specifying 'based on their unique user ID' and references 'list users tool' in the schema, suggesting when to use this tool (for a specific user) versus 'list_users' (for multiple users). However, it lacks explicit guidance on when to choose this over alternatives like 'get_contact' or 'get_team', and does not mention any exclusions or prerequisites.

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