Skip to main content
Glama

get_team

Retrieve detailed information about an existing team in your BoldSign organization, including team name, users, and creation date, by specifying 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

  • Executes the core logic of the get_team tool by initializing the BoldSign TeamsApi client with configuration, fetching the team details using the provided teamId, and returning the formatted MCP response or handling 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 input schema for the get_team tool, validating the required teamId parameter.
    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.',
      ),
    });
  • Registers the get_team tool definition, specifying its method name ('get_team'), description, input schema, and handler function.
    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);
      },
    };
  • Includes the get_team tool in the array of teams API tool definitions, which is later aggregated at higher levels.
    export const teamsApiToolsDefinitions: BoldSignTool[] = [getTeamToolDefinition, listTeamsToolDefinition];
  • Top-level aggregation of all tool definitions, including teamsApiToolsDefinitions which contains get_team.
    export const definitions: BoldSignTool[] = [
      ...contactsApiToolsDefinitions,
      ...documentsApiToolsDefinitions,
      ...templatesApiToolsDefinitions,
      ...usersApiToolsDefinitions,
      ...teamsApiToolsDefinitions,
    ];
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. It discloses this is a read operation ('Retrieve') and mentions what information is returned ('team-specific properties, such as team name, users, created date, and modified date'). However, it doesn't address potential behavioral aspects like error conditions, authentication requirements, rate limits, or what happens if the team ID is invalid.

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 efficiently structured in two sentences: the first states the purpose and scope, the second provides implementation details. Every word earns its place with no redundant information or unnecessary elaboration.

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

Completeness4/5

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

For a simple read operation with 100% schema coverage but no output schema, the description is reasonably complete. It explains what the tool does, what information it returns, and how to use it. The main gap is the lack of output format details, which would be helpful since there's no output schema provided.

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 fully documents the single parameter. The description adds minimal value beyond the schema by mentioning 'unique team ID' and that it's 'required,' but doesn't provide additional semantic context about parameter usage or constraints.

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 specific action ('Retrieve detailed information'), resource ('about an existing team in your BoldSign organization'), and scope ('by specifying the unique team ID'). It distinguishes from sibling tools like list_teams by focusing on single-team retrieval rather than 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?

The description provides clear context for when to use this tool ('by specifying the unique team ID') and implies an alternative (list_teams for getting team IDs). However, it doesn't explicitly state when NOT to use it or compare it directly to other get_* tools like get_user or get_contact.

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