Skip to main content
Glama

get_avatar_list

Retrieve a list of available avatars in VRChat via the Model Context Protocol, enabling AI-assisted avatar selection and control in virtual environments.

Instructions

Get a list of available avatars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration and inline handler for 'get_avatar_list'. Fetches avatars via avatarTools.getAllAvatars() and returns JSON string.
    server.tool(
      'get_avatar_list',
      'Get a list of available avatars.',
      {},
      async (_, extra) => {
        try {
          const ctx = createToolContext(extra);
          const avatars = await avatarTools.getAllAvatars();
          return { content: [{ type: 'text', text: JSON.stringify(avatars) }] };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `Error getting avatar list: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Helper method getAllAvatars() in AvatarTools class that calls wsClient.getAvatarlist() to fetch the avatar list with logging and error handling.
    /**
     * Get a list of all available avatars.
     *
     * @param ctx - MCP Context (optional)
     * @returns Promise resolving to an object with avatar IDs as keys and names as values
     */
    public async getAllAvatars(ctx?: ToolContext): Promise<{ [avatarId: string]: string }> {
      if (ctx) {
        await ctx.info('Getting list of available avatars');
      }
    
      try {
        const avatars = await this.wsClient.getAvatarlist();
        
        if (ctx) {
          const avatarCount = Object.keys(avatars).length;
          await ctx.info(`Found ${avatarCount} available avatars`);
        }
    
        return avatars;
      } catch (error) {
        const errorMsg = `Error getting avatar list: ${error instanceof Error ? error.message : String(error)}`;
        this.logger.error(errorMsg);
        if (ctx) {
          await ctx.error(errorMsg);
        }
        return {};
      }
    }
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 states the tool retrieves a list but doesn't describe what 'available avatars' means (e.g., user-owned, system-default, or all), whether it requires authentication, rate limits, or the format of the returned list. This leaves significant gaps for a tool with zero annotation coverage.

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, direct sentence with zero wasted words. It's front-loaded with the core action ('Get a list') and resource ('available avatars'), making it highly efficient and easy to parse.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what the list contains (e.g., avatar IDs, names, images), how it's structured, or any prerequisites for use. For a tool with no structured data to rely on, this leaves too much undefined for effective agent operation.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but this is appropriate given the schema's completeness. A baseline of 4 is applied as it adequately handles the lack of parameters without introducing confusion.

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 ('list of available avatars'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_avatar_name' or 'get_avatar_parameters', but the focus on listing all avatars is specific enough for basic clarity.

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_avatar_name' (which might retrieve details for a specific avatar) or 'set_avatar' (which modifies avatars). It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.

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/Krekun/vrchat-mcp-osc'

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