Skip to main content
Glama
aydinfer
by aydinfer

createEvent

Create interactive events in 3D scenes to trigger actions like animations, property changes, and function calls based on user interactions or scene conditions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
nameYesEvent name
typeYesEvent type
objectIdNoObject ID (if object-specific event)
actionsYesActions to perform when event is triggered

Implementation Reference

  • Executes the creation of a new event by preparing event data and making a POST request to the Spline API endpoint `/scenes/${sceneId}/events`. Returns formatted success or error response.
    async ({ sceneId, name, type, objectId, actions }) => {
      try {
        const eventData = {
          name,
          type,
          ...(objectId && { objectId }),
          actions,
        };
        
        const result = await apiClient.request('POST', `/scenes/${sceneId}/events`, eventData);
        
        return {
          content: [
            { 
              type: 'text', 
              text: `Event created successfully with ID: ${result.id}` 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error creating event: ${error.message}` 
            }
          ],
          isError: true
        };
      }
    }
  • Input schema using Zod for validating parameters: sceneId (required), name (required), type (enum of event types), objectId (optional), actions (array of action objects).
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      name: z.string().min(1).describe('Event name'),
      type: z.enum([
        'mouseDown', 'mouseUp', 'mouseOver', 'mouseOut', 'mouseMove',
        'touchStart', 'touchEnd', 'touchMove',
        'keyDown', 'keyUp',
        'collision', 'sceneStart', 'custom'
      ]).describe('Event type'),
      objectId: z.string().optional().describe('Object ID (if object-specific event)'),
      actions: z.array(z.object({
        type: z.enum([
          'triggerState', 'setProperty', 'playAnimation', 
          'callFunction', 'triggerEvent', 'setVariable'
        ]).describe('Action type'),
        target: z.string().optional().describe('Target ID (object, state, etc.)'),
        params: z.record(z.any()).optional().describe('Action parameters'),
      })).min(1).describe('Actions to perform when event is triggered'),
    },
  • Registers the 'createEvent' tool on the MCP server within the registerStateEventTools function.
    server.tool(
      'createEvent',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        name: z.string().min(1).describe('Event name'),
        type: z.enum([
          'mouseDown', 'mouseUp', 'mouseOver', 'mouseOut', 'mouseMove',
          'touchStart', 'touchEnd', 'touchMove',
          'keyDown', 'keyUp',
          'collision', 'sceneStart', 'custom'
        ]).describe('Event type'),
        objectId: z.string().optional().describe('Object ID (if object-specific event)'),
        actions: z.array(z.object({
          type: z.enum([
            'triggerState', 'setProperty', 'playAnimation', 
            'callFunction', 'triggerEvent', 'setVariable'
          ]).describe('Action type'),
          target: z.string().optional().describe('Target ID (object, state, etc.)'),
          params: z.record(z.any()).optional().describe('Action parameters'),
        })).min(1).describe('Actions to perform when event is triggered'),
      },
      async ({ sceneId, name, type, objectId, actions }) => {
        try {
          const eventData = {
            name,
            type,
            ...(objectId && { objectId }),
            actions,
          };
          
          const result = await apiClient.request('POST', `/scenes/${sceneId}/events`, eventData);
          
          return {
            content: [
              { 
                type: 'text', 
                text: `Event created successfully with ID: ${result.id}` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error creating event: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • src/index.js:90-90 (registration)
    Calls registerStateEventTools(server) to register all state and event tools, including createEvent.
    registerStateEventTools(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