Skip to main content
Glama
aydinfer
by aydinfer

applyMaterial

Assign materials to 3D objects in Spline scenes by specifying scene, object, and material IDs to customize visual appearance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
objectIdYesObject ID
materialIdYesMaterial ID

Implementation Reference

  • The async handler function for the 'applyMaterial' tool. It sends a POST request to apply the specified materialId to the objectId in the sceneId via the apiClient.
    async ({ sceneId, objectId, materialId }) => {
      try {
        await apiClient.request('POST', `/scenes/${sceneId}/objects/${objectId}/material`, {
          materialId
        });
        
        return {
          content: [
            { 
              type: 'text', 
              text: `Material ${materialId} applied to object ${objectId} successfully` 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error applying material: ${error.message}` 
            }
          ],
          isError: true
        };
      }
    }
  • Zod input schema defining parameters for the 'applyMaterial' tool: sceneId, objectId, and materialId.
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      objectId: z.string().min(1).describe('Object ID'),
      materialId: z.string().min(1).describe('Material ID'),
    },
  • The server.tool registration call for the 'applyMaterial' tool, including schema and handler function.
    // Apply a material to an object
    server.tool(
      'applyMaterial',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        objectId: z.string().min(1).describe('Object ID'),
        materialId: z.string().min(1).describe('Material ID'),
      },
      async ({ sceneId, objectId, materialId }) => {
        try {
          await apiClient.request('POST', `/scenes/${sceneId}/objects/${objectId}/material`, {
            materialId
          });
          
          return {
            content: [
              { 
                type: 'text', 
                text: `Material ${materialId} applied to object ${objectId} successfully` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error applying material: ${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