Skip to main content
Glama

voice

Control voice activation in VRChat using the MCP OSC server. Enable or disable voice chat for AI-driven avatar interactions in virtual reality environments.

Instructions

Toggle voice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'voice' tool. It sends a 'Voice' input press (1.0), waits 100ms, then releases (0.0) via the WebSocket client.
    public async voice(ctx?: ToolContext): Promise<string> {
      if (ctx) {
        await ctx.info('Voice');
      }
    
      try {
        // Send jump input
        const success = await this.wsClient.sendInput('Voice', 1.0);
        if (!success) {
          return 'Failed to Voice';
        }
    
        // Short delay for button press
        await delay(100);
    
        // Release jump button
        const releaseSuccess = await this.wsClient.sendInput('Voice', 0.0);
        if (!releaseSuccess) {
          return 'Voice initiated but failed to release button';
        }
    
        return 'Voice';
      } catch (error) {
        const errorMsg = `Error jumping: ${error instanceof Error ? error.message : String(error)}`;
        logger.error(errorMsg);
        return errorMsg;
      }
    }
  • The MCP server.tool registration for the 'voice' tool. It has no input parameters and calls the inputTools.voice handler.
    server.tool(
      'voice',
      'Toggle voice',
      {},
      async (_, extra) => {
        try {
          const ctx = createToolContext(extra);
          const result = await inputTools.voice(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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Toggle voice' implies a mutation action (changing state), but it doesn't specify what the toggle does (e.g., enable/disable voice, switch between voice modes), what the default state is, or any side effects like requiring permissions or affecting other tools. This leaves critical behavioral traits unclear for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description 'Toggle voice' is extremely concise at two words, which could be seen as efficient. However, it's arguably under-specified rather than appropriately concise, as it lacks necessary context for a mutation tool. It's front-loaded but doesn't earn its place with sufficient information, making it borderline between concise and inadequate.

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 complexity as a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'voice' refers to, what toggling entails, or what the expected outcome is. For a tool that likely changes system state, this minimal description fails to provide enough context for safe and effective 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is assigned because the schema fully handles the parameter semantics, and the description doesn't need to compensate for any gaps.

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 voice' is a tautology that essentially restates the tool name 'voice' with minimal elaboration. While it indicates an action ('toggle'), it doesn't specify what resource or system component is being toggled (e.g., voice chat, voice input, voice output), nor does it distinguish this tool from siblings like 'set_avatar_parameter' or 'set_emote_parameter' that might involve voice-related settings.

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

Usage Guidelines1/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 any context, prerequisites, or exclusions, such as whether it requires specific avatar settings or if it's only applicable in certain modes. Given siblings like 'set_avatar_parameter' that might control voice parameters, this lack of differentiation is a significant gap.

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