Skip to main content
Glama
Buu-AI

Buu AI MCP Server

team_get

Retrieve the personal team assigned to the current user on the Buu AI MCP Server.

Instructions

[PRIVATE] Get the personal team for the current user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'team_get' MCP tool, including inline handler that executes GraphQL query to get the current user's personal team and returns JSON or error.
    server.tool('team_get', '[PRIVATE] Get the personal team for the current user.', {}, async () => {
      try {
        const response = await client.request(getTeamQuery);
        return { content: [{ type: 'text', text: JSON.stringify(response) }] };
      } catch (error) {
        console.error('Error calling team_get:', error);
        return {
          isError: true,
          content: [{ type: 'text', text: `Error: Failed to retrieve team. ${error}` }],
        };
      }
    });
  • GraphQL query 'getTeamQuery' supporting the team_get handler by defining the structure to fetch the user's team data, including members, status, etc.
    const getTeamQuery = gql`
      query GetTeam {
        getTeam {
          ... 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 mentions the tool is '[PRIVATE]' (implying access restrictions) and targets 'the current user' (suggesting authentication needs), but lacks details on rate limits, error conditions, or what 'personal team' entails. This is insufficient for a tool with potential privacy implications.

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—just one sentence with no wasted words—and front-loaded with the key information. Every part of the sentence ('[PRIVATE]', 'Get', 'personal team', 'current user') contributes meaning, making it efficient and well-structured.

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

Completeness3/5

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

Given the tool has no parameters and no output schema, the description is minimally adequate but lacks depth. It doesn't explain what a 'personal team' is, what data is returned, or how it differs from other team-related tools. For a tool in a context with many siblings, more completeness would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the input schema coverage is 100% (as there are no parameters to cover). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate, as it doesn't detract from or conflict with the schema.

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 ('Get') and resource ('the personal team for the current user'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'team_get_all' or 'team_create', which would require more specificity to earn a 5.

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_get_all' or 'team_create', nor does it mention any prerequisites or context for usage. It only states what the tool does, not when it should be applied.

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