Skip to main content
Glama
aydinfer
by aydinfer

configurePostProcessing

Configure visual effects like bloom and depth of field for 3D scenes in Spline to enhance rendering quality and create cinematic visuals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
bloomNoBloom effect settings
depthOfFieldNoDepth of field settings

Implementation Reference

  • The handler function implementing the configurePostProcessing tool. It takes sceneId, bloom, and depthOfField parameters and returns a success or error message (placeholder implementation).
      async ({ sceneId, bloom, depthOfField }) => {
        try {
          // This would normally call the Spline API to configure post-processing
          // For now, just return a success message
          return {
            content: [
              { 
                type: 'text', 
                text: `Post-processing effects configured successfully` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error configuring post-processing: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • Zod schema defining input parameters for the configurePostProcessing tool: sceneId (required), bloom and depthOfField (optional objects with their settings).
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      bloom: z.object({
        enabled: z.boolean().default(false).describe('Enable bloom effect'),
        intensity: z.number().min(0).max(1).optional().default(0.5).describe('Bloom intensity'),
      }).optional().describe('Bloom effect settings'),
      depthOfField: z.object({
        enabled: z.boolean().default(false).describe('Enable depth of field'),
        focusDistance: z.number().min(0).optional().default(10).describe('Focus distance'),
        focalLength: z.number().min(0).optional().default(50).describe('Focal length'),
        bokehScale: z.number().min(0).optional().default(2).describe('Bokeh scale'),
      }).optional().describe('Depth of field settings'),
    },
  • Direct registration of the configurePostProcessing tool via server.tool() call within the registerLightingCameraTools function.
    server.tool(
      'configurePostProcessing',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        bloom: z.object({
          enabled: z.boolean().default(false).describe('Enable bloom effect'),
          intensity: z.number().min(0).max(1).optional().default(0.5).describe('Bloom intensity'),
        }).optional().describe('Bloom effect settings'),
        depthOfField: z.object({
          enabled: z.boolean().default(false).describe('Enable depth of field'),
          focusDistance: z.number().min(0).optional().default(10).describe('Focus distance'),
          focalLength: z.number().min(0).optional().default(50).describe('Focal length'),
          bokehScale: z.number().min(0).optional().default(2).describe('Bokeh scale'),
        }).optional().describe('Depth of field settings'),
      },
      async ({ sceneId, bloom, depthOfField }) => {
        try {
          // This would normally call the Spline API to configure post-processing
          // For now, just return a success message
          return {
            content: [
              { 
                type: 'text', 
                text: `Post-processing effects configured successfully` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error configuring post-processing: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • src/index.js:98-98 (registration)
    High-level registration in the main server setup, calling registerLightingCameraTools(server) which includes the configurePostProcessing tool.
    registerLightingCameraTools(server);
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