Skip to main content
Glama
aydinfer
by aydinfer

configureConditionalAction

Set up conditional logic in 3D scenes to trigger specific actions based on variable comparisons, enabling dynamic behavior in Spline designs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
actionIdYesAction ID
variableNameYesVariable name to check
conditionYesCondition to check
valueNoValue to compare against
trueActionIdsYesActions to trigger if condition is true
falseActionIdsNoActions to trigger if condition is false

Implementation Reference

  • Handler function that implements the configureConditionalAction tool logic: updates the action parameters for a conditional action type via API PUT request.
    async ({ sceneId, actionId, variableName, condition, value, trueActionIds, falseActionIds }) => {
      try {
        const parameters = {
          variableName,
          condition,
          value,
          trueActions: trueActionIds,
          ...(falseActionIds && { falseActions: falseActionIds }),
        };
        
        await apiClient.request('PUT', `/scenes/${sceneId}/actions/${actionId}`, {
          type: 'conditional',
          parameters
        });
        
        return {
          content: [
            { 
              type: 'text', 
              text: `Conditional action ${actionId} configured successfully` 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error configuring conditional action: ${error.message}` 
            }
          ],
          isError: true
        };
      }
  • Zod input schema defining parameters for the configureConditionalAction tool.
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      actionId: z.string().min(1).describe('Action ID'),
      variableName: z.string().min(1).describe('Variable name to check'),
      condition: z.enum(['equals', 'notEquals', 'greaterThan', 'lessThan', 'contains'])
        .describe('Condition to check'),
      value: z.any().describe('Value to compare against'),
      trueActionIds: z.array(z.string()).describe('Actions to trigger if condition is true'),
      falseActionIds: z.array(z.string()).optional().describe('Actions to trigger if condition is false'),
    },
  • Registration of the configureConditionalAction MCP tool within the registerActionTools function using server.tool().
    server.tool(
      'configureConditionalAction',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        actionId: z.string().min(1).describe('Action ID'),
        variableName: z.string().min(1).describe('Variable name to check'),
        condition: z.enum(['equals', 'notEquals', 'greaterThan', 'lessThan', 'contains'])
          .describe('Condition to check'),
        value: z.any().describe('Value to compare against'),
        trueActionIds: z.array(z.string()).describe('Actions to trigger if condition is true'),
        falseActionIds: z.array(z.string()).optional().describe('Actions to trigger if condition is false'),
      },
      async ({ sceneId, actionId, variableName, condition, value, trueActionIds, falseActionIds }) => {
        try {
          const parameters = {
            variableName,
            condition,
            value,
            trueActions: trueActionIds,
            ...(falseActionIds && { falseActions: falseActionIds }),
          };
          
          await apiClient.request('PUT', `/scenes/${sceneId}/actions/${actionId}`, {
            type: 'conditional',
            parameters
          });
          
          return {
            content: [
              { 
                type: 'text', 
                text: `Conditional action ${actionId} configured successfully` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error configuring conditional action: ${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