Skip to main content
Glama
aydinfer
by aydinfer

configureColorLayer

Set color properties for material layers in Spline 3D scenes by specifying color values and intensity to customize visual appearance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
materialIdYesMaterial ID
layerIdYesLayer ID
colorYesColor value (hex, rgb, or rgba)
intensityNoColor intensity

Implementation Reference

  • The handler function that executes the configureColorLayer tool logic: updates the specified color layer's parameters (color and optional intensity) using a PUT request to the API.
    async ({ sceneId, materialId, layerId, color, intensity }) => {
      try {
        const layerParams = {
          color,
          ...(intensity !== undefined && { intensity }),
        };
        
        await apiClient.request('PUT', `/scenes/${sceneId}/materials/${materialId}/layers/${layerId}`, {
          params: layerParams
        });
        
        return {
          content: [
            { 
              type: 'text', 
              text: `Color layer ${layerId} configured successfully` 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error configuring color layer: ${error.message}` 
            }
          ],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the configureColorLayer tool.
      sceneId: z.string().min(1).describe('Scene ID'),
      materialId: z.string().min(1).describe('Material ID'),
      layerId: z.string().min(1).describe('Layer ID'),
      color: z.string().describe('Color value (hex, rgb, or rgba)'),
      intensity: z.number().min(0).optional().default(1).describe('Color intensity'),
    },
  • Registration of the configureColorLayer tool using server.tool(), including schema and handler.
      'configureColorLayer',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        materialId: z.string().min(1).describe('Material ID'),
        layerId: z.string().min(1).describe('Layer ID'),
        color: z.string().describe('Color value (hex, rgb, or rgba)'),
        intensity: z.number().min(0).optional().default(1).describe('Color intensity'),
      },
      async ({ sceneId, materialId, layerId, color, intensity }) => {
        try {
          const layerParams = {
            color,
            ...(intensity !== undefined && { intensity }),
          };
          
          await apiClient.request('PUT', `/scenes/${sceneId}/materials/${materialId}/layers/${layerId}`, {
            params: layerParams
          });
          
          return {
            content: [
              { 
                type: 'text', 
                text: `Color layer ${layerId} configured successfully` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error configuring color layer: ${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