Skip to main content
Glama
Buu-AI

Buu AI MCP Server

team_update

Modify team details such as name and wallet address on Buu AI MCP Server to ensure accurate and updated team information.

Instructions

[PRIVATE] Update team data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name for the team
walletNoNew wallet address for the team

Implementation Reference

  • The async handler function that executes the core logic of the team_update tool by calling the GraphQL updateTeamDataMutation with provided name and/or wallet.
    async ({ name, wallet }) => {
      try {
        const response = await client.request(updateTeamDataMutation, { name, wallet });
        return { content: [{ type: 'text', text: JSON.stringify(response) }] };
      } catch (error) {
        console.error('Error calling team_update:', error);
        return {
          isError: true,
          content: [{ type: 'text', text: `Error: Failed to update team. ${error}` }],
        };
      }
    }
  • Zod input schema defining optional 'name' and 'wallet' parameters for the team_update tool.
    {
      name: z.string().optional().describe('New name for the team'),
      wallet: z.string().optional().describe('New wallet address for the team'),
    },
  • The server.tool call that registers the team_update tool, including its description, input schema, and inline handler function.
    server.tool(
      'team_update',
      '[PRIVATE] Update team data.',
      {
        name: z.string().optional().describe('New name for the team'),
        wallet: z.string().optional().describe('New wallet address for the team'),
      },
      async ({ name, wallet }) => {
        try {
          const response = await client.request(updateTeamDataMutation, { name, wallet });
          return { content: [{ type: 'text', text: JSON.stringify(response) }] };
        } catch (error) {
          console.error('Error calling team_update:', error);
          return {
            isError: true,
            content: [{ type: 'text', text: `Error: Failed to update team. ${error}` }],
          };
        }
      }
    );
  • GraphQL mutation definition used by the team_update handler to update team data.
    const updateTeamDataMutation = gql`
      mutation UpdateTeamData($name: String, $wallet: String) {
        updateTeamData(name: $name, wallet: $wallet) {
          ... 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?

No annotations are provided, so the description carries full burden. 'Update team data' implies a mutation operation but doesn't disclose behavioral traits like whether it requires specific permissions, if changes are reversible, what happens to existing data not mentioned in parameters, or any rate limits. The [PRIVATE] tag adds some context about visibility but doesn't explain operational behavior.

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 extremely concise with just two words plus a tag, which is appropriately sized for a simple update operation. However, the [PRIVATE] tag at the beginning is front-loaded but unexplained, and the description could benefit from slightly more context without becoming verbose.

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 inadequate. It doesn't explain what 'team data' encompasses beyond the two parameters, what the tool returns, or any prerequisites. With 2 parameters and siblings that handle related operations, more context is needed for proper 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%, with both parameters ('name' and 'wallet') clearly documented in the schema. The description adds no additional meaning beyond what the schema provides about these parameters, so it meets the baseline of 3 where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Update team data' which provides a clear verb ('Update') and resource ('team data'), but it's vague about what specific data is updated. It doesn't distinguish from sibling tools like 'team_update_member_role' or 'team_add_member' which also modify team data in different ways.

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. With siblings like 'team_create', 'team_get', 'team_update_member_role', and 'team_add_member', there's no indication whether this is for core team metadata updates versus membership changes or when it should be preferred over other update operations.

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