Skip to main content
Glama
Buu-AI

Buu AI MCP Server

team_create

Create a new team for the logged-in user by specifying a team name using the input schema, simplifying team management on the Buu AI MCP Server.

Instructions

[PRIVATE] Create a new team for the logged-in user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the new team

Implementation Reference

  • The asynchronous handler function for the 'team_create' tool that executes the GraphQL mutation to create a new team and handles the response or error.
    async ({ name }) => {
      try {
        const response = await client.request(createTeamMutation, { name });
        return { content: [{ type: 'text', text: JSON.stringify(response) }] };
      } catch (error) {
        console.error('Error calling team_create:', error);
        return {
          isError: true,
          content: [{ type: 'text', text: `Error: Failed to create team. ${error}` }],
        };
      }
    }
  • Zod input schema for the 'team_create' tool defining the required 'name' parameter.
    {
      name: z.string().describe('The name of the new team'),
    },
  • Registration of the 'team_create' tool using McpServer.tool method within registerTeamTools function.
    server.tool(
      'team_create',
      '[PRIVATE] Create a new team for the logged-in user.',
      {
        name: z.string().describe('The name of the new team'),
      },
      async ({ name }) => {
        try {
          const response = await client.request(createTeamMutation, { name });
          return { content: [{ type: 'text', text: JSON.stringify(response) }] };
        } catch (error) {
          console.error('Error calling team_create:', error);
          return {
            isError: true,
            content: [{ type: 'text', text: `Error: Failed to create team. ${error}` }],
          };
        }
      }
    );
  • GraphQL mutation query definition used by the team_create handler to create a new team.
    const createTeamMutation = gql`
      mutation CreateTeam($name: String!) {
        createTeam(name: $name) {
          ... 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)
    Top-level call to registerTeamTools function, which registers the 'team_create' tool along with other team tools.
    registerTeamTools(server, buuServerClient);
Behavior2/5

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

With no annotations, the description carries full burden but only states it creates a team for the logged-in user. It lacks details on permissions required, whether this is idempotent, what happens on failure, or the response format. For a mutation tool with zero annotation coverage, this is insufficient.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action, though the '[PRIVATE]' prefix is extraneous and could be omitted for better clarity.

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?

For a creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral nuances like whether team names must be unique, leaving significant gaps for an AI agent.

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 'name' parameter fully. The description adds no additional parameter information beyond what the schema provides, such as naming constraints or examples, meeting the baseline for high schema 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 ('Create') and resource ('a new team'), specifying it's for the logged-in user. It distinguishes from siblings like team_update or team_get by focusing on creation, though it doesn't explicitly contrast with them.

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 like team_add_member or team_update. It mentions the logged-in user context but doesn't specify prerequisites, exclusions, or comparative use cases with sibling tools.

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