Skip to main content
Glama
aydinfer
by aydinfer

createComprehensiveEvent

Create interactive events in 3D scenes to trigger actions based on user interactions like mouse clicks, keyboard input, collisions, or state changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
nameYesEvent name
typeYesEvent type
objectIdNoObject ID (if object-specific event)
parametersNoEvent specific parameters (e.g., key codes, trigger distances)
actionsYesActions to perform when event is triggered

Implementation Reference

  • The handler function that implements the core logic of the createComprehensiveEvent tool. It constructs the event data object from the provided parameters and uses the apiClient to POST it to the `/scenes/{sceneId}/events` endpoint, returning a success message with the new event ID or an error message.
      async ({ sceneId, name, type, objectId, parameters, actions }) => {
        try {
          const eventData = {
            name,
            type,
            ...(objectId && { objectId }),
            ...(parameters && { parameters }),
            actions,
          };
          
          const result = await apiClient.request('POST', `/scenes/${sceneId}/events`, eventData);
          
          return {
            content: [
              { 
                type: 'text', 
                text: `Event "${name}" created successfully with ID: ${result.id}` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error creating event: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • Zod validation schema defining the input structure for the createComprehensiveEvent tool, including required sceneId, name, type (comprehensive enum of all supported Spline event types), optional objectId and parameters, and required actions array.
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      name: z.string().min(1).describe('Event name'),
      type: z.enum([
        // Mouse events
        'mouseUp', 'mouseDown', 'mousePress', 'mouseHover', 
        // Keyboard events
        'keyUp', 'keyDown', 'keyPress',
        // Scroll and movement events
        'scroll', 'lookAt', 'follow',
        // Game control events
        'gameControls',
        // Physics and spatial events
        'distance', 'collision', 'triggerArea',
        // UI and state events
        'stateChange', 'variableChange', 'screenResize',
        // External integration events
        'apiUpdated', 'webhookCalled',
        // AI assistant events
        'aiAssistantListener', 'aiAssistantTrigger',
        // Scene events
        'sceneStart', 'sceneLoad', 'sceneUnload'
      ]).describe('Event type'),
      objectId: z.string().optional().describe('Object ID (if object-specific event)'),
      parameters: z.record(z.any()).optional().describe('Event specific parameters (e.g., key codes, trigger distances)'),
      actions: z.array(z.object({
        type: z.string().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'),
    },
  • The server.tool call that registers the createComprehensiveEvent tool with the MCP server, providing the tool name, input schema, and handler function.
    server.tool(
      'createComprehensiveEvent',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        name: z.string().min(1).describe('Event name'),
        type: z.enum([
          // Mouse events
          'mouseUp', 'mouseDown', 'mousePress', 'mouseHover', 
          // Keyboard events
          'keyUp', 'keyDown', 'keyPress',
          // Scroll and movement events
          'scroll', 'lookAt', 'follow',
          // Game control events
          'gameControls',
          // Physics and spatial events
          'distance', 'collision', 'triggerArea',
          // UI and state events
          'stateChange', 'variableChange', 'screenResize',
          // External integration events
          'apiUpdated', 'webhookCalled',
          // AI assistant events
          'aiAssistantListener', 'aiAssistantTrigger',
          // Scene events
          'sceneStart', 'sceneLoad', 'sceneUnload'
        ]).describe('Event type'),
        objectId: z.string().optional().describe('Object ID (if object-specific event)'),
        parameters: z.record(z.any()).optional().describe('Event specific parameters (e.g., key codes, trigger distances)'),
        actions: z.array(z.object({
          type: z.string().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, parameters, actions }) => {
        try {
          const eventData = {
            name,
            type,
            ...(objectId && { objectId }),
            ...(parameters && { parameters }),
            actions,
          };
          
          const result = await apiClient.request('POST', `/scenes/${sceneId}/events`, eventData);
          
          return {
            content: [
              { 
                type: 'text', 
                text: `Event "${name}" created successfully with ID: ${result.id}` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error creating event: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • src/index.js:96-96 (registration)
    Top-level call in the main server setup that invokes the registration of complete event tools, including createComprehensiveEvent, by calling registerCompleteEventTools(server).
    registerCompleteEventTools(server);
  • src/index.js:21-21 (registration)
    Import statement for the complete-event-tools module that defines and registers the createComprehensiveEvent tool.
    import { registerCompleteEventTools } from './tools/complete-event-tools.js';
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