Skip to main content
Glama

menu

Control and toggle menus in VRChat using the MCP OSC server, enabling AI-assisted avatar interactions and settings adjustments in virtual reality environments.

Instructions

Toggle Menu.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function in InputTools class that executes the menu toggle by sending QuickMenuToggleLeft input press and release via WebSocket client.
    public async menu(ctx?: ToolContext): Promise<string> {
      if (ctx) {
        await ctx.info('Menu');
      }
    
      try {
        // Send jump input
        const success = await this.wsClient.sendInput('QuickMenuToggleLeft', 1.0);
        if (!success) {
          return 'Failed to Menu';
        }
    
        // Short delay for button press
        await delay(100);
    
        // Release jump button
        const releaseSuccess = await this.wsClient.sendInput('QuickMenuToggleLeft', 0.0);
        if (!releaseSuccess) {
          return 'Menu initiated but failed to release button';
        }
    
        return 'Menu';
      } catch (error) {
        const errorMsg = `Error Menu: ${error instanceof Error ? error.message : String(error)}`;
        logger.error(errorMsg);
        return errorMsg;
      }
    }
  • MCP tool registration for 'menu' tool, which creates a ToolContext and delegates execution to inputTools.menu().
    server.tool(
      'menu',
      'Toggle Menu.',
      {},
      async (_, extra) => {
        try {
          const ctx = createToolContext(extra);
          const result = await inputTools.menu(ctx);
          return { content: [{ type: 'text', text: result }] };
        } catch (error) {
          return { 
            content: [{ 
              type: 'text', 
              text: `Error jumping: ${error instanceof Error ? error.message : String(error)}` 
            }],
            isError: true
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Toggle Menu' implies a state-changing operation but doesn't specify whether this affects UI visibility, game state, or user experience. No information about side effects, permissions needed, or what 'toggling' actually does is provided.

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 maximally concise with just two words that directly state the action. There's zero wasted language or unnecessary elaboration for a simple toggle operation.

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 no annotations, no output schema, and zero parameters, the description is incomplete. While conciseness is appropriate, 'Toggle Menu' lacks sufficient context about what menu system this operates on, what visual or functional changes occur, and how this integrates with the sibling tools (many of which are avatar/game related).

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 zero parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to compensate for any parameter documentation gaps since there are no parameters to document.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Toggle Menu' is a tautology that essentially restates the tool name 'menu' without providing meaningful context about what resource or system the menu belongs to. While 'toggle' is a specific verb, it doesn't distinguish this tool from siblings or clarify what type of menu is being toggled (UI menu, game menu, etc.).

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?

No guidance is provided about when to use this tool versus alternatives. Given the sibling tools include avatar-related operations (get_avatar_list, set_avatar), movement commands (jump, move_avatar), and communication tools (send_message, voice), there's no indication whether this menu toggle relates to UI navigation, game interfaces, or other contexts.

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