Skip to main content
Glama
Synctest-hub

BoldSign MCP Server

get_team

Retrieve detailed team information from your BoldSign organization, including team name, users, and creation date, by providing the unique team ID.

Instructions

Retrieve detailed information about an existing team in your BoldSign organization. This API provides access to team-specific properties, such as team name, users, created date, and modified date, by specifying the unique team ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdYesRequired. The unique identifier (ID) of the team to retrieve. This can be obtained from the list teams tool.

Implementation Reference

  • Core handler function that initializes the BoldSign TeamsApi client, retrieves the team by ID, and returns a formatted McpResponse or handles errors.
    async function getTeamHandler(payload: GetTeamSchemaType): Promise<McpResponse> {
      try {
        const teamsApi = new TeamsApi();
        teamsApi.basePath = configuration.getBasePath();
        teamsApi.setApiKey(configuration.getApiKey());
        const teamResponse: TeamResponse = await teamsApi.getTeam(payload.teamId);
        return handleMcpResponse({
          data: teamResponse,
        });
      } catch (error: any) {
        return handleMcpError(error);
      }
    }
  • Zod schema defining the input parameters for the get_team tool: requires a teamId string.
    const GetTeamSchema = z.object({
      teamId: commonSchema.InputIdSchema.describe(
        'Required. The unique identifier (ID) of the team to retrieve. This can be obtained from the list teams tool.',
      ),
    });
  • Tool definition object registered as BoldSignTool with method 'get_team', description, input schema, and wrapper handler calling the core getTeamHandler.
    export const getTeamToolDefinition: BoldSignTool = {
      method: ToolNames.GetTeam.toString(),
      name: 'Get team',
      description:
        'Retrieve detailed information about an existing team in your BoldSign organization. This API provides access to team-specific properties, such as team name, users, created date, and modified date, by specifying the unique team ID.',
      inputSchema: GetTeamSchema,
      async handler(args: unknown): Promise<McpResponse> {
        return await getTeamHandler(args as GetTeamSchemaType);
      },
    };
  • Central collection of all tool definitions, including the teams tools (which contain get_team), exported for use in MCP server.
    export const definitions: BoldSignTool[] = [
      ...contactsApiToolsDefinitions,
      ...documentsApiToolsDefinitions,
      ...templatesApiToolsDefinitions,
      ...usersApiToolsDefinitions,
      ...teamsApiToolsDefinitions,
    ];
  • src/index.ts:22-60 (registration)
    MCP server request handlers for ListTools (exposes get_team via definitions) and CallTool (executes get_team handler by method name matching).
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: definitions.map((toolDefinition: BoldSignTool) => {
        return {
          name: toolDefinition.method,
          description: toolDefinition.description,
          inputSchema: zodToJsonSchema(toolDefinition.inputSchema),
        };
      }),
    }));
    
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const toolName = request.params.name;
      const tool = definitions.find((t) => t.method === toolName);
    
      if (!tool) {
        throw new McpError(ErrorCode.MethodNotFound, `Unknown tool: ${toolName}`);
      }
    
      const args = request.params.arguments;
      const schemaResult = tool.inputSchema.safeParse(args);
    
      if (!schemaResult.success) {
        throw new McpError(
          ErrorCode.InvalidParams,
          `Invalid parameters for tool ${toolName}: ${schemaResult.error.message}`,
        );
      }
    
      try {
        const result = await tool.handler(args);
        return {
          content: [{ type: 'text', text: `${toJsonString(result)}` }],
        };
      } catch (error) {
        console.error('[Error] Failed to fetch data:', error);
        const errorMessage = error instanceof Error ? error.message : String(error);
        throw new McpError(ErrorCode.InternalError, `API error: ${errorMessage}`);
      }
    });
Behavior3/5

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

With no annotations, the description carries full burden. It discloses this is a read operation ('Retrieve') and mentions access to specific properties, but lacks details on permissions, rate limits, or error handling. It's adequate but has gaps for a tool with no annotation support.

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?

It's front-loaded with the core purpose in the first sentence, followed by supporting details. Every sentence adds value: the first defines the action, the second lists properties and ID requirement. No wasted words.

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 simple read tool with 1 parameter and no output schema, the description covers purpose and usage adequately. However, with no annotations, it could benefit from more behavioral context like response format or error cases, making it minimally viable but not fully comprehensive.

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 the teamId parameter fully. The description adds no additional parameter details beyond implying it's used for retrieval, meeting the baseline of 3 when 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 verb ('Retrieve') and resource ('detailed information about an existing team'), specifying it's for a BoldSign organization. It distinguishes from siblings like list_teams by focusing on a single team via ID, not listing multiple teams.

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?

It provides clear context: use this to get details for a specific team by ID, implying an alternative is list_teams for multiple teams. However, it doesn't explicitly state when not to use it or name alternatives directly, keeping it at a 4.

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