Skip to main content
Glama
Buu-AI

Buu AI MCP Server

team_remove_member

Manage team membership on the Buu AI MCP Server by removing a member using their address. Maintain accurate team composition with this tool.

Instructions

[PRIVATE] Remove a member from the team.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memberYesAddress of the team member to remove

Implementation Reference

  • Handler function that sends the removeTeamMemberMutation GraphQL request using the provided member address and returns the response or formatted error.
    async ({ member }) => {
      try {
        const response = await client.request(removeTeamMemberMutation, { member });
        return { content: [{ type: 'text', text: JSON.stringify(response) }] };
      } catch (error) {
        console.error('Error calling team_remove_member:', error);
        return {
          isError: true,
          content: [{ type: 'text', text: `Error: Failed to remove team member. ${error}` }],
        };
      }
    }
  • Zod input schema defining the required 'member' parameter as an Ethereum address string.
    {
      member: z.string().describe('Address of the team member to remove'),
    },
  • Direct registration of the 'team_remove_member' tool on the MCP server with name, description, schema, and handler.
    server.tool(
      'team_remove_member',
      '[PRIVATE] Remove a member from the team.',
      {
        member: z.string().describe('Address of the team member to remove'),
      },
      async ({ member }) => {
        try {
          const response = await client.request(removeTeamMemberMutation, { member });
          return { content: [{ type: 'text', text: JSON.stringify(response) }] };
        } catch (error) {
          console.error('Error calling team_remove_member:', error);
          return {
            isError: true,
            content: [{ type: 'text', text: `Error: Failed to remove team member. ${error}` }],
          };
        }
      }
    );
  • GraphQL mutation definition used to remove a specified member from the team and fetch updated team details or error.
    const removeTeamMemberMutation = gql`
      mutation RemoveTeamMember($member: String!) {
        removeTeamMember(member: $member) {
          ... on Team {
            _id
            type
            name
            creator
            wallet
            members {
              address
              role
              status
            }
            available
            pending
            confirmed
            updatedAt
            createdAt
          }
          ... on HandledError {
            code
            message
          }
        }
      }
    `;
  • src/index.ts:49-49 (registration)
    High-level registration call that invokes registerTeamTools, thereby registering team_remove_member and other team tools to the main MCP server instance.
    registerTeamTools(server, buuServerClient);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is destructive (likely yes, but not confirmed), what permissions are required, how it affects team data, or what happens on success/failure. The '[PRIVATE]' tag adds some context but is vague.

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 extremely concise with just one sentence plus a tag, front-loaded with the core action. Every word earns its place, with no wasted text, making it efficient for quick understanding.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks crucial context like what 'remove' entails (e.g., irreversible deletion, archiving), expected outcomes, error conditions, or how it interacts with sibling tools, leaving significant gaps for agent usage.

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 'member' parameter as 'Address of the team member to remove'. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high coverage.

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 ('Remove') and target ('a member from the team'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'team_update_member_role' which might also affect team membership, missing full sibling distinction.

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., needing admin permissions), when not to use it, or how it differs from related tools like 'team_update_member_role' for role changes instead of removal.

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