Skip to main content
Glama
aydinfer
by aydinfer

generateEventListenerCode

Generate JavaScript event listener code for Spline 3D scenes to handle user interactions like mouse clicks, keyboard inputs, and touch events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
eventNameYesEvent name

Implementation Reference

  • Registration of the MCP tool 'generateEventListenerCode' including input schema (sceneId, eventName) and handler that delegates to runtimeManager.generateEventListenerCode and returns the generated code as text content.
    server.tool(
      'generateEventListenerCode',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        eventName: z.enum([
          'mouseDown', 'mouseUp', 'mouseOver', 'mouseOut', 'mouseMove',
          'touchStart', 'touchEnd', 'touchMove',
          'keyDown', 'keyUp', 'collision', 'sceneStart'
        ]).describe('Event name'),
      },
      async ({ sceneId, eventName }) => {
        try {
          const code = runtimeManager.generateEventListenerCode(sceneId, eventName);
          
          return {
            content: [
              { 
                type: 'text', 
                text: code 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error generating code: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • Zod schema for tool inputs: sceneId (string) and eventName (enum of supported Spline events).
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      eventName: z.enum([
        'mouseDown', 'mouseUp', 'mouseOver', 'mouseOut', 'mouseMove',
        'touchStart', 'touchEnd', 'touchMove',
        'keyDown', 'keyUp', 'collision', 'sceneStart'
      ]).describe('Event name'),
    },
  • MCP tool handler function that invokes runtimeManager.generateEventListenerCode and formats the result as MCP content response.
    async ({ sceneId, eventName }) => {
      try {
        const code = runtimeManager.generateEventListenerCode(sceneId, eventName);
        
        return {
          content: [
            { 
              type: 'text', 
              text: code 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error generating code: ${error.message}` 
            }
          ],
          isError: true
        };
      }
  • Helper method in RuntimeManager class that generates template JavaScript code for loading a Spline scene and attaching an event listener for the specified eventName, with example handlers for common objects.
      generateEventListenerCode(sceneId, eventName) {
        const sceneUrl = `https://prod.spline.design/${sceneId}/scene.splinecode`;
        
        return `
    import { Application } from '@splinetool/runtime';
    
    // Create a new Application instance
    const canvas = document.getElementById('canvas3d');
    const spline = new Application(canvas);
    
    // Load the scene
    spline.load('${sceneUrl}').then(() => {
      console.log('Scene loaded successfully');
      
      // Add event listener
      spline.addEventListener('${eventName}', (e) => {
        console.log('Event triggered:', e);
        
        // Get information about the target object
        const targetObject = e.target;
        console.log('Target object:', targetObject.name, targetObject.id);
        
        // Respond to the event
        if (targetObject.name === 'Cube') {
          // Handle cube-specific event
          targetObject.scale.multiplyScalar(1.1); // Grow by 10%
        } else if (targetObject.name === 'Sphere') {
          // Handle sphere-specific event
          targetObject.material.color.set('#ff0000'); // Change to red
        }
        
        // You can also emit events on other objects
        const otherObject = spline.findObjectByName('OtherObject');
        if (otherObject) {
          otherObject.emitEvent('mouseDown');
        }
      });
    });
    `;
      }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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?

Tool has no description.

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/aydinfer/spline-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server