Skip to main content
Glama
aydinfer
by aydinfer

getRuntimeSetup

Configure runtime environment settings for the 3D design tool to enable scene operations, model imports, and animation creation through natural language commands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'getRuntimeSetup' tool using server.tool() with empty input schema and inline async handler.
    server.tool(
      'getRuntimeSetup',
      {},
      async () => {
        try {
          const setupCode = runtimeManager.generateRuntimeSetup();
          
          return {
            content: [
              { 
                type: 'text', 
                text: setupCode 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error generating setup code: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • The inline async handler function that executes the tool logic by calling runtimeManager.generateRuntimeSetup() and returning the formatted response or error.
    async () => {
      try {
        const setupCode = runtimeManager.generateRuntimeSetup();
        
        return {
          content: [
            { 
              type: 'text', 
              text: setupCode 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error generating setup code: ${error.message}` 
            }
          ],
          isError: true
        };
      }
    }
  • RuntimeManager.generateRuntimeSetup() method providing the core logic: installation commands and complete HTML example for Spline runtime setup.
      generateRuntimeSetup() {
        return `
    # Installing @splinetool/runtime
    npm install @splinetool/runtime
    
    # For React projects, also install
    npm install @splinetool/react-spline
    
    # Basic HTML setup:
    <!DOCTYPE html>
    <html>
    <head>
      <meta charset="UTF-8">
      <title>Spline Scene</title>
      <style>
        html, body { margin: 0; height: 100%; overflow: hidden; }
        #canvas3d { width: 100%; height: 100%; display: block; }
      </style>
    </head>
    <body>
      <canvas id="canvas3d"></canvas>
      <script type="module">
        import { Application } from '@splinetool/runtime';
        
        // Create application
        const canvas = document.getElementById('canvas3d');
        const spline = new Application(canvas);
        
        // Load scene
        spline.load('https://prod.spline.design/YOUR_SCENE_ID/scene.splinecode')
          .then(() => {
            console.log('Scene loaded');
            // Interact with scene here
          });
      </script>
    </body>
    </html>
    `;
      }
  • src/index.js:104-104 (registration)
    Top-level call to registerRuntimeTools(server) in main MCP server setup, which includes registration of getRuntimeSetup.
    registerRuntimeTools(server);
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