Skip to main content
Glama
aydinfer
by aydinfer

configureOpenAI

Configure OpenAI integration in Spline 3D scenes to generate AI responses, map variables, and automate interactions when scenes load.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
modelNoOpenAI model to usegpt-3.5-turbo
apiKeyNoOpenAI API key (uses env var if not provided)
promptYesSystem prompt/behavior for the AI
requestOnStartNoWhether to call OpenAI when scene loads
variableMappingsNoMappings from OpenAI response to Spline variables

Implementation Reference

  • Direct registration of the 'configureOpenAI' MCP tool, including inline Zod input schema and async handler function that configures OpenAI integration for a Spline scene via API call.
    server.tool(
      'configureOpenAI',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        model: z.enum(['gpt-3.5-turbo', 'gpt-4-turbo', 'gpt-4o-mini', 'gpt-4o'])
          .default('gpt-3.5-turbo').describe('OpenAI model to use'),
        apiKey: z.string().optional().describe('OpenAI API key (uses env var if not provided)'),
        prompt: z.string().min(1).describe('System prompt/behavior for the AI'),
        requestOnStart: z.boolean().optional().default(false)
          .describe('Whether to call OpenAI when scene loads'),
        variableMappings: z.array(z.object({
          responseField: z.string().describe('Field from API response'),
          variableName: z.string().describe('Spline variable name'),
        })).optional().describe('Mappings from OpenAI response to Spline variables'),
      },
      async ({ sceneId, model, apiKey, prompt, requestOnStart, variableMappings }) => {
        try {
          const openaiConfig = {
            model,
            apiKey: apiKey || process.env.OPENAI_API_KEY,
            prompt,
            requestOnStart: requestOnStart || false,
            ...(variableMappings && { variableMappings }),
          };
          
          const result = await apiClient.request('POST', `/scenes/${sceneId}/openai`, openaiConfig);
          
          return {
            content: [
              { 
                type: 'text', 
                text: `OpenAI integration configured successfully with ID: ${result.id}` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error configuring OpenAI: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • The core handler function implementing the 'configureOpenAI' tool logic: constructs config from params, calls Spline API to configure OpenAI integration, returns success/error response.
      async ({ sceneId, model, apiKey, prompt, requestOnStart, variableMappings }) => {
        try {
          const openaiConfig = {
            model,
            apiKey: apiKey || process.env.OPENAI_API_KEY,
            prompt,
            requestOnStart: requestOnStart || false,
            ...(variableMappings && { variableMappings }),
          };
          
          const result = await apiClient.request('POST', `/scenes/${sceneId}/openai`, openaiConfig);
          
          return {
            content: [
              { 
                type: 'text', 
                text: `OpenAI integration configured successfully with ID: ${result.id}` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error configuring OpenAI: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • Zod input schema defining parameters for the 'configureOpenAI' tool: sceneId, model, apiKey, prompt, requestOnStart, variableMappings.
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      model: z.enum(['gpt-3.5-turbo', 'gpt-4-turbo', 'gpt-4o-mini', 'gpt-4o'])
        .default('gpt-3.5-turbo').describe('OpenAI model to use'),
      apiKey: z.string().optional().describe('OpenAI API key (uses env var if not provided)'),
      prompt: z.string().min(1).describe('System prompt/behavior for the AI'),
      requestOnStart: z.boolean().optional().default(false)
        .describe('Whether to call OpenAI when scene loads'),
      variableMappings: z.array(z.object({
        responseField: z.string().describe('Field from API response'),
        variableName: z.string().describe('Spline variable name'),
      })).optional().describe('Mappings from OpenAI response to Spline variables'),
    },
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