Skip to main content
Glama

get_user_information

Retrieve user profile information from BAND, including the option to fetch user details within a specific band context by providing a band key.

Instructions

Get user profile information from BAND. Optionally specify a band_key to get user info within a specific band context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
band_keyNoBand ID to get the user's profile from a specific band. If not provided, the default profile of the user will be returned.

Output Schema

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

Implementation Reference

  • The core handler function that executes the get_user_information tool by calling the BAND API /v2/profile endpoint and formatting the response.
    export async function handleToolCall(band_key?: string) {
      const params: Record<string, unknown> = {};
      if (band_key) (params as Record<string, unknown>).band_key = band_key;
      const profile = await bandApiClient.get<BandUserProfile>(
        "/v2/profile",
        params
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(profile, null, 2),
          },
        ],
      };
    }
  • The ToolDefinition object defining the tool's name, description, input schema (optional band_key), and output schema for get_user_information.
    export const ToolDefinition: Tool = {
      name: "get_user_information",
      description:
        "Get user profile information from BAND. Optionally specify a band_key to get user info within a specific band context.",
      inputSchema: {
        type: "object",
        properties: {
          band_key: {
            type: "string",
            title: "Band Key",
            description:
              "Band ID to get the user's profile from a specific band. If not provided, the default profile of the user will be returned.",
          },
        },
        required: [],
      },
      outputSchema: {
        type: "object",
        properties: {
          success: {
            type: "boolean",
            description: "Indicates if the operation was successful.",
          },
          data: {
            type: "object",
            description: "User profile data returned from BAND API.",
            properties: {
              user_key: {
                type: "string",
                description: "User ID.",
              },
              name: {
                type: "string",
                description: "User's name.",
              },
              profile_image_url: {
                type: "string",
                description: "URL of a profile image.",
              },
              is_app_member: {
                type: "boolean",
                description:
                  "Boolean value indicating whether the user account is connected to your app or not.",
              },
              message_allowed: {
                type: "boolean",
                description:
                  "Boolean value indicating whether the user allowed to receive messages or not.",
              },
            },
          },
        },
        required: ["success", "data"],
      },
    };
  • src/tools.ts:15-28 (registration)
    Registration of all tools including get_user_information via profile.ToolDefinition in the bandTools export array.
    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/tools.ts:34-36 (registration)
    Routing logic in the main handleToolCall switch statement that dispatches get_user_information calls to the profile module's handler.
    case "get_user_information":
      return profile.handleToolCall(a.band_key as string | undefined);
    case "get_bands":
  • TypeScript interface defining the expected shape of the BAND user profile response.
    interface BandUserProfile {
      name: string;
      profile_image_url?: string;
      is_app_member: boolean;
      message_allowed: boolean;
    }
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 mentions that the tool retrieves information (implying read-only) and describes the band_key's effect, but fails to address critical aspects like authentication needs, rate limits, error conditions, or what the output contains (though an output schema exists). For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 two concise sentences that efficiently convey the core purpose and key parameter usage. It is front-loaded with the main action and avoids unnecessary details, making it easy to parse. Every sentence adds value without redundancy.

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

Completeness4/5

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

Given the tool's low complexity (1 optional parameter) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the purpose and parameter context adequately. However, it could improve by addressing behavioral aspects like authentication or error handling, which are not covered by annotations or schema.

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 the parameter 'band_key' fully documented in the schema. The description adds minimal value by restating the optionality and effect of band_key ('Optionally specify... to get user info within a specific band context'), but doesn't provide additional semantics beyond what the schema already covers. This meets 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 verb ('Get') and resource ('user profile information from BAND'), making the purpose evident. It distinguishes this tool from siblings like 'get_bands' or 'get_posts' by focusing on user profiles rather than other data types. However, it doesn't explicitly differentiate from non-sibling alternatives or specify the exact scope of 'profile information' beyond the band context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning the optional 'band_key' parameter for context-specific retrieval, suggesting when to use it (for band-specific vs. default profiles). However, it lacks explicit guidance on when to choose this tool over others (e.g., vs. 'get_bands' for band-level data) or any prerequisites/exclusions, leaving usage somewhat inferred rather than clearly defined.

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