Skip to main content
Glama

send_message

Send a message to the VRChat chatbox directly or populate it for later use. Enables AI-driven interactions in virtual reality environments.

Instructions

Send a message to the VRChat chatbox.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage to send
send_immediatelyNoSend immediately or just populate chatbox

Implementation Reference

  • MCP tool registration for 'send_message', including inline schema (Zod) and handler function that delegates to inputTools.sendChatboxMessage
    server.tool(
      'send_message',
      'Send a message to the VRChat chatbox.',
      {
        message: z.string().describe('Message to send'),
        send_immediately: z.boolean().default(true).describe('Send immediately or just populate chatbox')
      },
      async ({ message, send_immediately }, extra) => {
        try {
          const ctx = createToolContext(extra);
          const result = await inputTools.sendChatboxMessage(message, send_immediately, ctx);
          return { content: [{ type: 'text', text: result }] };
        } catch (error) {
          return { 
            content: [{ 
              type: 'text', 
              text: `Error sending message: ${error instanceof Error ? error.message : String(error)}` 
            }],
            isError: true
          };
        }
      }
    );
  • Core handler logic in InputTools.sendChatboxMessage, wraps wsClient call and provides user feedback
    public async sendChatboxMessage(
      message: string,
      sendImmediately: boolean = true,
      ctx?: ToolContext
    ): Promise<string> {
      if (ctx) {
        await ctx.info(`Sending message: "${message}" (immediate: ${sendImmediately})`);
      }
    
      try {
        const success = await this.wsClient.sendChatboxMessage(message, sendImmediately);
        if (success) {
          return `Message sent: "${message}"`;
        } else {
          return `Failed to send message: "${message}"`;
        }
      } catch (error) {
        const errorMsg = `Error sending message: ${error instanceof Error ? error.message : String(error)}`;
        logger.error(errorMsg);
        return errorMsg;
      }
    }
  • WebSocket client method that sends 'chatbox/sendMessage' RPC to relay server
    public async sendChatboxMessage(
      message: string,
      sendImmediately: boolean = true,
      notification: boolean = true
    ): Promise<boolean> {
      const response = await this.sendRequest<{ success: boolean }>('chatbox/sendMessage', {
        message,
        immediate: sendImmediately,
        notification
      });
      this.logger.info(`Chatbox message response: ${JSON.stringify(response)}`);
      return response.success;
    }
  • Relay server RPC handler for 'chatbox/sendMessage' that delegates to oscClient.send_chatbox
    case 'chatbox/sendMessage':
      // Send a chatbox message
      const message = data.message as string;
      const sendImmediately = data.immediate as boolean ?? true;
      const notification = data.notification as boolean ?? true;
    
      if (!message) {
        response.error = { message: 'Missing message text' };
      } else {
        const result = this.oscClient.send_chatbox(message, sendImmediately, notification);
        response.data = { success: result };
      }
      break;
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. While 'Send a message' implies a write operation, the description lacks details on permissions, rate limits, side effects (e.g., chat visibility), or response behavior. The mention of 'chatbox' adds some context, but overall behavioral traits are minimally covered.

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 purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand quickly with zero waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (a write operation with two parameters), lack of annotations, and no output schema, the description is minimally adequate. It covers the basic action but lacks depth on behavioral aspects and output expectations, making it complete enough for a simple tool but with clear gaps for informed usage.

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?

Schema description coverage is 100%, so the schema already documents both parameters ('message' and 'send_immediately') with clear descriptions. The tool description adds no additional parameter semantics beyond what the schema provides, adhering to the baseline score when schema coverage is high.

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 ('Send a message') and the target ('to the VRChat chatbox'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from potential alternatives or siblings, as none of the listed sibling tools appear to handle chat functionality directly, so differentiation isn't explicitly needed but could be implied by context.

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, prerequisites, or contextual constraints. It simply states what the tool does without indicating appropriate scenarios or exclusions, leaving usage entirely to inference from the tool name and basic functionality.

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