Skip to main content
Glama
aydinfer
by aydinfer

configureApi

Set up HTTP API endpoints for Spline 3D scenes to fetch data and map responses to scene variables for dynamic content integration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
nameYesAPI name
methodYesHTTP method
urlYesAPI endpoint URL
headersNoHTTP headers
bodyNoRequest body (for POST, PUT, PATCH)
queryParamsNoURL query parameters
requestOnStartNoWhether to call API when scene loads
variableMappingsNoMappings from API response to Spline variables

Implementation Reference

  • Main execution handler for the 'configureApi' tool. Parses inputs, constructs API configuration object, calls the apiClient helper, and formats MCP response.
      async ({ 
        sceneId, 
        name, 
        method, 
        url, 
        headers, 
        body, 
        queryParams, 
        requestOnStart, 
        variableMappings 
      }) => {
        try {
          const apiConfig = {
            name,
            method,
            url,
            ...(headers && { headers }),
            ...(body && { body }),
            ...(queryParams && { queryParams }),
            requestOnStart: requestOnStart || false,
            ...(variableMappings && { variableMappings }),
          };
          
          const result = await apiClient.configureApi(sceneId, apiConfig);
          
          return {
            content: [
              { 
                type: 'text', 
                text: `API connection configured successfully with ID: ${result.id}` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error configuring API: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • Zod input schema validating parameters for the configureApi tool including sceneId, name, method, url, optional headers/body/queryParams/requestOnStart/variableMappings.
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      name: z.string().min(1).describe('API name'),
      method: z.enum(['GET', 'POST', 'PUT', 'DELETE', 'HEAD', 'OPTIONS', 'PATCH'])
        .describe('HTTP method'),
      url: z.string().url().describe('API endpoint URL'),
      headers: z.record(z.string()).optional().describe('HTTP headers'),
      body: z.record(z.any()).optional().describe('Request body (for POST, PUT, PATCH)'),
      queryParams: z.record(z.string()).optional().describe('URL query parameters'),
      requestOnStart: z.boolean().optional().default(false)
        .describe('Whether to call API when scene loads'),
      variableMappings: z.array(z.object({
        responseField: z.string().describe('Field from API response'),
        variableName: z.string().describe('Spline variable name'),
        variableType: z.enum(['string', 'number', 'boolean']).describe('Variable type'),
      })).optional().describe('Mappings from API response to Spline variables'),
    },
  • MCP tool registration via server.tool('configureApi', schema, handler) within registerApiWebhookTools function.
    server.tool(
      'configureApi',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        name: z.string().min(1).describe('API name'),
        method: z.enum(['GET', 'POST', 'PUT', 'DELETE', 'HEAD', 'OPTIONS', 'PATCH'])
          .describe('HTTP method'),
        url: z.string().url().describe('API endpoint URL'),
        headers: z.record(z.string()).optional().describe('HTTP headers'),
        body: z.record(z.any()).optional().describe('Request body (for POST, PUT, PATCH)'),
        queryParams: z.record(z.string()).optional().describe('URL query parameters'),
        requestOnStart: z.boolean().optional().default(false)
          .describe('Whether to call API when scene loads'),
        variableMappings: z.array(z.object({
          responseField: z.string().describe('Field from API response'),
          variableName: z.string().describe('Spline variable name'),
          variableType: z.enum(['string', 'number', 'boolean']).describe('Variable type'),
        })).optional().describe('Mappings from API response to Spline variables'),
      },
      async ({ 
        sceneId, 
        name, 
        method, 
        url, 
        headers, 
        body, 
        queryParams, 
        requestOnStart, 
        variableMappings 
      }) => {
        try {
          const apiConfig = {
            name,
            method,
            url,
            ...(headers && { headers }),
            ...(body && { body }),
            ...(queryParams && { queryParams }),
            requestOnStart: requestOnStart || false,
            ...(variableMappings && { variableMappings }),
          };
          
          const result = await apiClient.configureApi(sceneId, apiConfig);
          
          return {
            content: [
              { 
                type: 'text', 
                text: `API connection configured successfully with ID: ${result.id}` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error configuring API: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • Supporting method in SplineApiClient that sends POST request to Spline API endpoint /scenes/{sceneId}/apis to configure the API connection.
    async configureApi(sceneId, apiConfig) {
      return this.request('POST', `/scenes/${sceneId}/apis`, apiConfig);
    }
  • src/index.js:91-91 (registration)
    Top-level call in main server setup that invokes registerApiWebhookTools(server), thereby registering the configureApi tool.
    registerApiWebhookTools(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