Skip to main content
Glama
aydinfer
by aydinfer

getEvents

Retrieve events from a specific Spline 3D scene by providing the scene ID to access animation triggers and interactive elements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID

Implementation Reference

  • MCP tool handler for 'getEvents': registers the tool, validates input with Zod schema (sceneId), fetches events using apiClient.getEvents(sceneId), returns JSON stringified events or error message.
    // Get all events in a scene
    server.tool(
      'getEvents',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
      },
      async ({ sceneId }) => {
        try {
          const events = await apiClient.getEvents(sceneId);
          return {
            content: [
              { 
                type: 'text', 
                text: JSON.stringify(events, null, 2) 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error retrieving events: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • src/index.js:90-90 (registration)
    Top-level registration of state event tools (including getEvents) by calling registerStateEventTools(server).
    registerStateEventTools(server);
  • Helper method apiClient.getEvents(sceneId) that performs a GET request to the Spline API endpoint `/scenes/${sceneId}/events` to retrieve all events in the scene.
    /**
     * List events in a scene
     * @param {string} sceneId - ID of the scene
     * @returns {Promise<Array>} - List of events
     */
    async getEvents(sceneId) {
      return this.request('GET', `/scenes/${sceneId}/events`);
    }
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