Cinema4D MCP

Overview Schema Source Related Servers Discussions Admin

apply_shader

Create and apply a shader material (noise, gradient, fresnel, etc.) to a specified object or material in Cinema 4D, enabling quick material assignment for scene rendering.

Instructions

Create and apply a specialized shader material.

Args:
    shader_type: Type of shader (noise, gradient, fresnel, etc)
    material_name: Optional name of material to apply shader to
    object_name: Optional name of object to apply the material to

Input Schema

TableJSON Schema

Name	Required	Description	Default
`object_name`	No
`shader_type`	Yes
`material_name`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 10, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears the full burden of behavioral disclosure. It states that the tool 'creates and applies' a shader, but it does not reveal side effects such as whether applying a shader overwrites an existing material, what happens if material_name is omitted, or whether the operation is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficient with no fluff, using a brief Args list to convey the three parameters. It earns slightly less than 5 because it leads with a generic verb phrase rather than a more descriptive single sentence, and the sibling ambiguity is unaddressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With sibling tools create_material and apply_material present, the description does not explain when to use this combined action versus those alternatives. There is no mention of side effects, what happens when optional parameters are omitted, or how the shader type maps to creation behavior. Given the tool creates and mutates scene state accruing both material and object, these gaps are meaningful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description gives one-line meanings for all three parameters, plus domain examples for shader_type ('noise, gradient, fresnel, etc'). This adds value but remains shallow – for example, it doesn't clarify what happens when material_name or object_name are omitted, or how shader_type values map to actual materials.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource: 'create and apply a specialized shader material.' It distinguishes the tool as performing both creation and application, though the boundary versus sibling tools create_material and apply_material is not explicitly drawn.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus create_material or apply_material, which are obvious adjacent siblings. The description does not explain prerequisites, when the combined behavior is appropriate, or when the alternatives should be chosen.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.