Skip to main content
Glama
aydinfer
by aydinfer

createParametricObject

Create 3D objects like cubes, spheres, and cylinders in Spline scenes with customizable positioning and shape parameters for 3D design projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
typeYesObject type
nameYesObject name
positionNoObject position
parametersNoShape-specific parameters

Implementation Reference

  • src/index.js:24-24 (registration)
    Imports the registerDesignTools function which registers the createParametricObject tool.
    import { registerDesignTools } from './tools/design-tools.js';
  • src/index.js:101-101 (registration)
    Calls registerDesignTools to register the createParametricObject tool on the MCP server.
    registerDesignTools(server);
  • Zod input schema for the createParametricObject tool defining sceneId, type, name, position, and parameters.
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      type: z.enum([
        'cube', 'sphere', 'cylinder', 'cone', 'torus', 
        'plane', 'circle', 'polygon', 'star', 'ring'
      ]).describe('Object type'),
      name: z.string().min(1).describe('Object name'),
      position: z.object({
        x: z.number().default(0).describe('X position'),
        y: z.number().default(0).describe('Y position'),
        z: z.number().default(0).describe('Z position'),
      }).optional().describe('Object position'),
      parameters: z.record(z.any()).optional().describe('Shape-specific parameters'),
    },
  • Handler function that simulates creating a parametric object by returning a success message (mock implementation).
    async ({ sceneId, type, name, position, parameters }) => {
      try {
        // This would normally call the Spline API to create a parametric object
        // For now, just return a success message
        return {
          content: [
            { 
              type: 'text', 
              text: `Parametric object "${name}" of type "${type}" created successfully` 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error creating parametric object: ${error.message}` 
            }
          ],
          isError: true
        };
      }
    }
  • The server.tool call that registers the createParametricObject tool with its schema and handler.
      'createParametricObject',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        type: z.enum([
          'cube', 'sphere', 'cylinder', 'cone', 'torus', 
          'plane', 'circle', 'polygon', 'star', 'ring'
        ]).describe('Object type'),
        name: z.string().min(1).describe('Object name'),
        position: z.object({
          x: z.number().default(0).describe('X position'),
          y: z.number().default(0).describe('Y position'),
          z: z.number().default(0).describe('Z position'),
        }).optional().describe('Object position'),
        parameters: z.record(z.any()).optional().describe('Shape-specific parameters'),
      },
      async ({ sceneId, type, name, position, parameters }) => {
        try {
          // This would normally call the Spline API to create a parametric object
          // For now, just return a success message
          return {
            content: [
              { 
                type: 'text', 
                text: `Parametric object "${name}" of type "${type}" created successfully` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error creating parametric object: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
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