Skip to main content
Glama
sawa-zen

VRChat MCP Server

vrchat_get_current_user

Retrieve your VRChat user information to access your profile details through the VRChat MCP Server.

Instructions

Retrieve your own VRChat user information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'vrchat_get_current_user' tool. It authenticates the VRChat client, fetches the current user data via the API, and returns it as a JSON-formatted text block. Includes error handling.
    async () => {
      try {
        await vrchatClient.auth()
        const response = await vrchatClient.authApi.getCurrentUser()
        const user = response.data
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(user, null, 2)
          }]
        }
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: 'Failed to retrieve user: ' + error
          }]
        }
      }
    }
  • Direct registration of the 'vrchat_get_current_user' tool with the MCP server inside the createUsersTools function, including name, description, empty input schema, and inline handler.
    server.tool(
      'vrchat_get_current_user',
      'Retrieve your own VRChat user information',
      {}, // No parameters
      async () => {
        try {
          await vrchatClient.auth()
          const response = await vrchatClient.authApi.getCurrentUser()
          const user = response.data
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(user, null, 2)
            }]
          }
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: 'Failed to retrieve user: ' + error
            }]
          }
        }
      }
    )
  • src/main.ts:29-29 (registration)
    Invocation of createUsersTools in the main server setup, which registers the users tools including 'vrchat_get_current_user'.
    createUsersTools(server, vrchatClient)
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 it 'retrieves' information, implying a read-only operation, but doesn't clarify aspects like authentication requirements (e.g., whether it works without login), rate limits, error conditions (e.g., if no user is logged in), or the format of the returned data. This leaves significant gaps in understanding how the tool behaves in practice.

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 function without any fluff or redundancy. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place, and there's no wasted verbiage.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but incomplete. It doesn't address behavioral aspects like authentication needs or error handling, and without an output schema, it doesn't hint at what information is returned (e.g., user ID, display name, avatar details). For a tool that likely interacts with user state, more context is needed to ensure reliable use.

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 has 100% description coverage (though empty). The description appropriately doesn't discuss parameters, as there are none to explain. It could theoretically mention that no inputs are required, but this is implicit, so a baseline score of 4 is justified for not adding unnecessary information.

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 ('Retrieve') and the resource ('your own VRChat user information'), making the purpose immediately understandable. It distinguishes itself from siblings like 'vrchat_get_friends_list' or 'vrchat_get_notifications' by specifying it returns the current user's data rather than other entities. However, it doesn't specify what specific information is included (e.g., username, avatar, status), which prevents a perfect score.

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. It doesn't mention prerequisites (e.g., authentication status), compare it to similar tools (e.g., if other tools might return user data in different contexts), or indicate scenarios where it's particularly useful (e.g., checking login status or fetching profile details). This lack of contextual direction leaves the agent to infer usage based on the name 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/sawa-zen/vrchat-mcp'

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