Skip to main content
Glama
aydinfer
by aydinfer

triggerEvent

Activate specific events within 3D scenes to control animations and interactions in Spline design projects using scene and event identifiers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
eventIdYesEvent ID
eventDataNoEvent data

Implementation Reference

  • Handler function that executes the 'triggerEvent' tool logic by invoking apiClient.triggerEvent and formatting the response as MCP content.
    async ({ sceneId, eventId, eventData }) => {
      try {
        await apiClient.triggerEvent(sceneId, eventId, eventData || {});
        
        return {
          content: [
            { 
              type: 'text', 
              text: `Event ${eventId} triggered successfully` 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error triggering event: ${error.message}` 
            }
          ],
          isError: true
        };
      }
  • Input schema using Zod for validating parameters of the 'triggerEvent' tool.
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      eventId: z.string().min(1).describe('Event ID'),
      eventData: z.record(z.any()).optional().describe('Event data'),
    },
  • Registration of the 'triggerEvent' MCP tool on the server, including schema and handler.
    server.tool(
      'triggerEvent',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        eventId: z.string().min(1).describe('Event ID'),
        eventData: z.record(z.any()).optional().describe('Event data'),
      },
      async ({ sceneId, eventId, eventData }) => {
        try {
          await apiClient.triggerEvent(sceneId, eventId, eventData || {});
          
          return {
            content: [
              { 
                type: 'text', 
                text: `Event ${eventId} triggered successfully` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error triggering event: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
  • apiClient helper method that performs the HTTP POST request to the Spline API to trigger the specified event.
    async triggerEvent(sceneId, eventId, eventData = {}) {
      return this.request('POST', `/scenes/${sceneId}/events/${eventId}/trigger`, eventData);
    }
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