Skip to main content
Glama

apply_mograph_fields

Create and apply MoGraph fields in Cinema 4D to control object behavior with spherical, box, cylindrical, linear, radial, or noise field types.

Instructions

Create and apply a MoGraph Field.

Args:
    field_type: Type of field (spherical, box, cylindrical, linear, radial, noise)
    target: Optional target object to apply the field to
    field_name: Optional name for the field
    parameters: Optional parameters for the field (strength, falloff)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
field_typeYes
targetNo
field_nameNo
parametersNo

Implementation Reference

  • The 'apply_mograph_fields' tool is defined and registered as an MCP tool using the '@mcp.tool()' decorator. It handles creating and applying MoGraph fields in Cinema 4D by sending a command over a connection context.
    @mcp.tool()
    async def apply_mograph_fields(
        field_type: str,
        target: Optional[str] = None,
        field_name: Optional[str] = None,
        parameters: Optional[Dict[str, Any]] = None,
        ctx: Context = None,
    ) -> str:
        """
        Create and apply a MoGraph Field.
    
        Args:
            field_type: Type of field (spherical, box, cylindrical, linear, radial, noise)
            target: Optional target object to apply the field to
            field_name: Optional name for the field
            parameters: Optional parameters for the field (strength, falloff)
        """
        async with c4d_connection_context() as connection:
            if not connection.connected:
                return "❌ Not connected to Cinema 4D"
    
            # Build the command with required parameters
            command = {"command": "apply_mograph_fields", "field_type": field_type}
    
            # Add optional parameters
            if target:
                command["target_name"] = target
    
            if field_name:
                command["field_name"] = field_name
    
            if parameters:
                command["parameters"] = parameters
    
            # Log the command for debugging
            logger.info(f"Sending apply_mograph_fields command: {command}")
    
            # Send the command to Cinema 4D
            response = send_to_c4d(connection, command)
    
            if "error" in response:
                logger.error(f"Error applying field: {response['error']}")
            return format_c4d_response(response, "apply_mograph_fields")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a creation and application action but doesn't specify if this is a destructive operation, what permissions are required, how it affects the scene, or any rate limits. The description adds minimal context beyond the basic action, leaving significant gaps in understanding the tool's behavior.

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 front-loaded with the purpose in the first sentence, followed by a parameter list. It's efficient with minimal waste, though the parameter descriptions could be more detailed. The structure is clear, but it lacks additional context that might be necessary for full understanding.

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?

Given the complexity (4 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It covers the basic action and parameters but misses behavioral details, usage context, and output expectations. For a tool that creates and applies fields in a 3D scene, more information on effects and integration with sibling tools is needed.

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?

The description lists parameters and their types (e.g., 'field_type' with enum-like values), adding meaning beyond the input schema, which has 0% description coverage. However, it doesn't fully compensate for the coverage gap—for example, 'parameters' is vaguely described as 'Optional parameters for the field (strength, falloff)' without detailing structure or defaults. This provides some value but is incomplete.

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?

The description clearly states the tool's purpose: 'Create and apply a MoGraph Field.' It specifies the action (create and apply) and the resource (MoGraph Field), which is specific and actionable. However, it doesn't differentiate from sibling tools like 'add_effector' or 'apply_dynamics' that might involve similar operations, keeping it from a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It lists parameters but doesn't mention prerequisites, context (e.g., when MoGraph Fields are needed in a scene), or comparisons to sibling tools like 'add_effector' or 'apply_dynamics'. This leaves the agent without clear usage instructions.

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/ttiimmaacc/cinema4d-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server