Skip to main content
Glama
sawa-zen

VRChat MCP Server

vrchat_get_notifications

Retrieve VRChat notifications to monitor friend requests, messages, and platform updates, enabling users to stay informed about social interactions and account activity.

Instructions

Retrieve a list of VRChat notifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOnly send notifications of this type. Use "all" for all types. This parameter no longer does anything and is deprecated.
sentNoReturn notifications sent by the user. Must be false or omitted.
hiddenNoWhether to return hidden or non-hidden notifications. True only allowed on type "friendRequest".
afterNoOnly return notifications sent after this Date. Ignored if type is "friendRequest".
nNoThe number of objects to return. Default: 60, Max: 100
offsetNoA zero-based offset from the default object sorting from where to start.

Implementation Reference

  • The handler function for the 'vrchat_get_notifications' tool. Authenticates the VRChat client, calls getNotifications on notificationsApi with provided parameters, returns JSON stringified data or error message.
    async (params) => {
      try {
        await vrchatClient.auth()
        const response = await vrchatClient.notificationsApi.getNotifications(
          params.type,
          params.sent,
          params.hidden,
          params.after,
          params.n || 60,
          params.offset || 0,
        )
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2)
          }]
        }
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: 'Failed to retrieve notifications: ' + error
          }]
        }
      }
    }
  • Input schema using Zod for validating parameters of the 'vrchat_get_notifications' tool.
    {
      type: z.string().optional().describe(
        'Only send notifications of this type. Use "all" for all types. This parameter no longer does anything and is deprecated.'
      ),
      sent: z.boolean().optional().describe(
        'Return notifications sent by the user. Must be false or omitted.'
      ),
      hidden: z.boolean().optional().describe(
        'Whether to return hidden or non-hidden notifications. True only allowed on type "friendRequest".'
      ),
      after: z.string().optional().describe(
        'Only return notifications sent after this Date. Ignored if type is "friendRequest".'
      ),
      n: z.number().min(1).max(100).optional().describe(
        'The number of objects to return. Default: 60, Max: 100'
      ),
      offset: z.number().min(0).optional().describe(
        'A zero-based offset from the default object sorting from where to start.'
      ),
    },
  • Registers the 'vrchat_get_notifications' tool on the MCP server with name, description, schema, and handler function.
    server.tool(
      // Name
      'vrchat_get_notifications',
      // Description
      'Retrieve a list of VRChat notifications.',
      {
        type: z.string().optional().describe(
          'Only send notifications of this type. Use "all" for all types. This parameter no longer does anything and is deprecated.'
        ),
        sent: z.boolean().optional().describe(
          'Return notifications sent by the user. Must be false or omitted.'
        ),
        hidden: z.boolean().optional().describe(
          'Whether to return hidden or non-hidden notifications. True only allowed on type "friendRequest".'
        ),
        after: z.string().optional().describe(
          'Only return notifications sent after this Date. Ignored if type is "friendRequest".'
        ),
        n: z.number().min(1).max(100).optional().describe(
          'The number of objects to return. Default: 60, Max: 100'
        ),
        offset: z.number().min(0).optional().describe(
          'A zero-based offset from the default object sorting from where to start.'
        ),
      },
      async (params) => {
        try {
          await vrchatClient.auth()
          const response = await vrchatClient.notificationsApi.getNotifications(
            params.type,
            params.sent,
            params.hidden,
            params.after,
            params.n || 60,
            params.offset || 0,
          )
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(response.data, null, 2)
            }]
          }
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: 'Failed to retrieve notifications: ' + error
            }]
          }
        }
      }
    )
  • src/main.ts:37-37 (registration)
    Calls createNotificationsTools to register the notifications tools, including 'vrchat_get_notifications', on the main MCP server.
    createNotificationsTools(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 but only states the basic action. It doesn't mention authentication requirements, rate limits, pagination behavior (beyond what's implied by parameters), error conditions, or what the returned list contains, leaving significant gaps for a tool with 6 parameters.

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, clear sentence that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, 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?

For a tool with 6 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on authentication, rate limits, return format, error handling, and how it differs from sibling tools, making it incomplete for effective agent use despite the concise structure.

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?

The schema description coverage is 100%, with each parameter well-documented in the input schema (e.g., 'type' is deprecated, 'sent' must be false). The description adds no additional parameter semantics beyond the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 'retrieve' and the resource 'list of VRChat notifications', making the purpose unambiguous. However, it doesn't differentiate this tool from potential siblings like 'vrchat_get_invite_message' or 'vrchat_list_invite_messages' which might also retrieve notification-like data, leaving room for improvement in sibling distinction.

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. Given siblings like 'vrchat_get_invite_message' and 'vrchat_list_invite_messages', it doesn't clarify if this is the primary notification retrieval method or if there are specific scenarios where other tools are preferred, offering no usage context.

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