Skip to main content
Glama
aydinfer
by aydinfer

generateVariableCode

Generate code to create and set variables in Spline 3D scenes, enabling dynamic control of scene parameters and values for interactive 3D designs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
variableNameYesVariable name
valueNoVariable value

Implementation Reference

  • MCP tool registration for 'generateVariableCode', including input schema (Zod) and handler function that calls runtimeManager to generate code and returns it as text content.
    server.tool(
      'generateVariableCode',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        variableName: z.string().min(1).describe('Variable name'),
        value: z.any().describe('Variable value'),
      },
      async ({ sceneId, variableName, value }) => {
        try {
          const code = runtimeManager.generateVariableCode(sceneId, variableName, value);
          
          return {
            content: [
              { 
                type: 'text', 
                text: code 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error generating code: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • The core handler function in RuntimeManager class that generates the JavaScript code snippet for loading a Spline scene and manipulating the specified variable (setting value, getting, listening, and example animation).
      generateVariableCode(sceneId, variableName, value) {
        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');
      
      // Set variable value
      spline.setVariable('${variableName}', ${JSON.stringify(value)});
      
      // Get variable value
      const currentValue = spline.getVariable('${variableName}');
      console.log('Current value:', currentValue);
      
      // Listen for variable changes
      spline.addEventListener('variableChanged', (e) => {
        if (e.variableName === '${variableName}') {
          console.log('Variable changed:', e.variableName, e.value);
          // React to variable change
        }
      });
      
      // Example: Change variable over time
      let count = 0;
      const interval = setInterval(() => {
        count++;
        spline.setVariable('${variableName}', count);
        
        if (count >= 10) {
          clearInterval(interval);
        }
      }, 1000);
    });
    `;
      }
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