Skip to main content
Glama
aydinfer
by aydinfer

configureFog

Configure fog effects in 3D scenes by setting color, density, and distance parameters to create atmospheric depth and visual ambiance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
enabledNoWhether fog is enabled
colorNoFog color (hex)#cccccc
densityNoFog density
nearNoNear distance
farNoFar distance

Implementation Reference

  • The asynchronous handler function for the 'configureFog' tool. It takes fog configuration parameters and simulates configuring fog in a Spline scene by returning a success message, with error handling.
    async ({ sceneId, enabled, color, density, near, far }) => {
      try {
        // This would normally call the Spline API to configure fog
        // For now, just return a success message
        return {
          content: [
            { 
              type: 'text', 
              text: `Fog ${enabled ? 'enabled' : 'disabled'} successfully` 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error configuring fog: ${error.message}` 
            }
          ],
          isError: true
        };
      }
    }
  • Zod validation schema for the input parameters of the configureFog tool.
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      enabled: z.boolean().default(true).describe('Whether fog is enabled'),
      color: z.string().optional().default('#cccccc').describe('Fog color (hex)'),
      density: z.number().min(0).max(1).optional().default(0.1).describe('Fog density'),
      near: z.number().min(0).optional().default(1).describe('Near distance'),
      far: z.number().min(0).optional().default(100).describe('Far distance'),
    },
  • The server.tool call that registers the 'configureFog' tool, including its name, schema, and handler function, within the registerLightingCameraTools module.
      'configureFog',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        enabled: z.boolean().default(true).describe('Whether fog is enabled'),
        color: z.string().optional().default('#cccccc').describe('Fog color (hex)'),
        density: z.number().min(0).max(1).optional().default(0.1).describe('Fog density'),
        near: z.number().min(0).optional().default(1).describe('Near distance'),
        far: z.number().min(0).optional().default(100).describe('Far distance'),
      },
      async ({ sceneId, enabled, color, density, near, far }) => {
        try {
          // This would normally call the Spline API to configure fog
          // For now, just return a success message
          return {
            content: [
              { 
                type: 'text', 
                text: `Fog ${enabled ? 'enabled' : 'disabled'} successfully` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error configuring fog: ${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