Skip to main content
Glama

jump

Trigger avatar jumps in VRChat using the MCP OSC bridge, enabling AI-driven control for dynamic interactions in virtual reality environments.

Instructions

Make the avatar jump.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'jump' tool. Sends 'Jump' input with value 1.0, waits 100ms, then releases with 0.0 via wsClient. Returns success or error messages.
    public async jump(ctx?: ToolContext): Promise<string> {
      if (ctx) {
        await ctx.info('Jumping');
      }
    
      try {
        // Send jump input
        const success = await this.wsClient.sendInput('Jump', 1.0);
        if (!success) {
          return 'Failed to jump';
        }
    
        // Short delay for button press
        await delay(100);
    
        // Release jump button
        const releaseSuccess = await this.wsClient.sendInput('Jump', 0.0);
        if (!releaseSuccess) {
          return 'Jump initiated but failed to release button';
        }
    
        return 'Jumped';
      } catch (error) {
        const errorMsg = `Error jumping: ${error instanceof Error ? error.message : String(error)}`;
        logger.error(errorMsg);
        return errorMsg;
      }
    }
  • MCP server registration of the 'jump' tool with empty input schema. Creates ToolContext and calls inputTools.jump(ctx), handling errors.
    server.tool(
      'jump',
      'Make the avatar jump.',
      {},
      async (_, extra) => {
        try {
          const ctx = createToolContext(extra);
          const result = await inputTools.jump(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. While 'Make the avatar jump' implies an action, it doesn't describe what 'jump' means in this context, whether it's instantaneous or has duration, what visual/audio effects occur, or whether it affects other avatar 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 maximally concise at just three words, front-loading the essential action without any wasted words. Every element ('Make', 'the avatar', 'jump') earns its place in conveying the tool's purpose.

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?

For a zero-parameter action tool with no annotations and no output schema, the description provides the basic action but lacks context about what 'jump' entails behaviorally. It's adequate as a minimum viable description but has clear gaps in explaining the tool's effects and behavior.

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 with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents the empty parameter set.

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 ('Make') and the target ('the avatar jump'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'move_avatar' or 'set_avatar_parameter' that might involve avatar movement or state changes.

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. There's no mention of prerequisites, timing considerations, or how it differs from similar sibling tools like 'move_avatar' or 'set_avatar_parameter'.

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