Skip to main content
Glama

get_bands

Retrieve the list of BAND groups you have joined to access and manage your community memberships.

Instructions

Get the list of bands that the user joined from BAND.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesUser's bands data returned from BAND API.
successYesIndicates if the operation was successful.

Implementation Reference

  • The main handler function that executes the tool by calling the BAND API endpoint '/v2/bands' and returning the JSON stringified response.
    export async function handleToolCall() {
        const bandsData = await bandApiClient.get<BandsResponse>('/v2/bands');
        return {
            content: [{
                type: "text",
                text: JSON.stringify(bandsData, null, 2)
            }]
        };
    }
  • Defines the tool metadata including name, description, empty input schema, and detailed output schema matching the BAND API response structure.
    export const ToolDefinition : Tool = {
        name: "get_bands",
        description: "Get the list of bands that the user joined from BAND.",
        inputSchema: {
            type: "object",
            properties: {},
            required: []
        },
        outputSchema: {
            type: "object",
            properties: {
            success: {
                type: "boolean",
                description: "Indicates if the operation was successful."
            },
            data: {
                type: "object",
                description: "User's bands data returned from BAND API.",
                properties: {
                bands: {
                    type: "array",
                    description: "List of bands the user joined.",
                    items: {
                    type: "object",
                    properties: {
                        band_key: {
                        type: "string",
                        description: "Band ID."
                        },
                        name: {
                        type: "string",
                        description: "Band name."
                        },
                        description: {
                        type: "string",
                        description: "Band description."
                        },
                        cover_url: {
                        type: "string",
                        description: "URL of a cover image."
                        },
                        band_url: {
                        type: "string",
                        description: "URL of a band."
                        },
                        member_count: {
                        type: "number",
                        description: "Number of band members."
                        },
                        created_at: {
                        type: "number",
                        description: "Band creation time in timestamp format."
                        }
                    }
                    }
                }
                }
            }
            },
            required: ["success", "data"]
        }
    };
  • src/tools.ts:36-37 (registration)
    Registers the handler dispatch in the main tool switch statement, calling bands.handleToolCall() for 'get_bands'.
    case "get_bands":
      return bands.handleToolCall();
  • src/tools.ts:15-28 (registration)
    Registers the get_bands ToolDefinition (from bands.ToolDefinition) into the array of all available BAND tools.
    export const bandTools: Tool[] = [
      profile.ToolDefinition,
      bands.ToolDefinition,
      posts.ToolDefinition,
      post.ToolDefinition,
      comments.ToolDefinition,
      permissions.ToolDefinition,
      albums.ToolDefinition,
      photos.ToolDefinition,
      writeComment.ToolDefinition,
      writePost.ToolDefinition,
      removePost.ToolDefinition,
      removeComment.ToolDefinition,
    ];
  • src/bands/index.ts:1-5 (registration)
    Re-exports the ToolDefinition and handleToolCall from tool.ts for use in src/tools.ts.
    import {ToolDefinition, handleToolCall} from "./tool.js";
    
    const bands = {ToolDefinition, handleToolCall}
    
    export default bands;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states a read operation ('Get'), implying it's likely safe, but doesn't mention permissions, rate limits, or what 'joined from BAND' entails. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 0 parameters, 100% schema coverage, and an output schema, the description is minimally adequate. However, it lacks context about the user's relationship to bands (e.g., what 'joined' means) and behavioral details, which could be important for an agent to use it correctly. With no annotations, it should do more to compensate.

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 with 100% schema description coverage, so the schema fully documents the inputs. The description doesn't need to add parameter details, and it doesn't introduce confusion. A baseline of 4 is appropriate for a zero-parameter tool with complete 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 ('Get') and resource ('list of bands that the user joined from BAND'), making the purpose understandable. It doesn't explicitly differentiate from siblings like 'get_albums' or 'get_user_information', but the resource specificity helps. A 5 would require explicit sibling differentiation.

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 'get_user_information' or other 'get_' siblings. It lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage based on tool names alone.

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

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/kanghouchao/band-mcp-server'

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