Skip to main content
Glama
Buu-AI

Buu AI MCP Server

team_add_member

Add a new member to your team by specifying their address using the team_add_member tool on the Buu AI MCP Server, ensuring smooth collaboration and team management.

Instructions

[PRIVATE] Add a new member to the team.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memberYesAddress of the new team member

Implementation Reference

  • The handler function that executes the team_add_member tool logic by calling the GraphQL addTeamMemberMutation.
    async ({ member }) => {
      try {
        const response = await client.request(addTeamMemberMutation, { member });
        return { content: [{ type: 'text', text: JSON.stringify(response) }] };
      } catch (error) {
        console.error('Error calling team_add_member:', error);
        return {
          isError: true,
          content: [{ type: 'text', text: `Error: Failed to add team member. ${error}` }],
        };
      }
    }
  • Zod input schema defining the 'member' parameter for the team_add_member tool.
    {
      member: z.string().describe('Address of the new team member'),
    },
  • Registration of the team_add_member tool using server.tool, including name, description, schema, and handler.
      'team_add_member',
      '[PRIVATE] Add a new member to the team.',
      {
        member: z.string().describe('Address of the new team member'),
      },
      async ({ member }) => {
        try {
          const response = await client.request(addTeamMemberMutation, { member });
          return { content: [{ type: 'text', text: JSON.stringify(response) }] };
        } catch (error) {
          console.error('Error calling team_add_member:', error);
          return {
            isError: true,
            content: [{ type: 'text', text: `Error: Failed to add team member. ${error}` }],
          };
        }
      }
    );
  • GraphQL mutation definition used by the team_add_member handler to add a member to the team.
    const addTeamMemberMutation = gql`
      mutation Mutation($member: String!) {
        addTeamMember(member: $member) {
          ... on Team {
            _id
            type
            name
            creator
            wallet
            members {
              address
              role
              status
            }
            available
            pending
            confirmed
            updatedAt
            createdAt
          }
          ... on HandledError {
            code
            message
          }
        }
      }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs an addition (implying a write/mutation operation) but doesn't disclose critical traits: whether it requires admin permissions, what happens on success (e.g., confirmation message, member details), error conditions (e.g., invalid address, duplicate member), or side effects (e.g., notifications sent). The '[PRIVATE]' tag suggests restricted access but lacks specifics.

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 very concise—a single sentence with the core action front-loaded. The '[PRIVATE]' tag is efficiently placed at the start. However, it's arguably too brief, lacking necessary details for a mutation tool, which slightly reduces its effectiveness despite the clean structure.

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

Completeness2/5

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

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It doesn't explain what the tool returns (e.g., success status, member object), error handling, or permissions required. For a tool that modifies team membership, this leaves significant gaps in understanding how to use it correctly and 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?

Schema description coverage is 100%, with the single parameter 'member' documented as 'Address of the new team member' in the schema. The description adds no additional meaning beyond this—it doesn't clarify the format of 'Address' (e.g., email, user ID) or provide examples. Since the schema handles the parameter documentation adequately, the baseline score of 3 is appropriate, but the description doesn't compensate with extra context.

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 ('Add') and target resource ('a new member to the team'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'team_remove_member' and 'team_update_member_role' by focusing on addition rather than removal or modification. However, it doesn't specify what constitutes a 'member' (e.g., user ID, email) or the team context, leaving some ambiguity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., team must exist, user permissions), exclusions (e.g., cannot add duplicate members), or related tools like 'team_create' (for creating a team first) or 'team_update_member_role' (for modifying roles after addition). The '[PRIVATE]' tag hints at restricted access but doesn't clarify usage context.

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

Related 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/Buu-AI/buu-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server