Skip to main content
Glama

inspect_redshift_materials

Inspect Redshift materials in Cinema 4D scenes to analyze names, assignments, colors, descriptions, and node graphs with fallback options when Redshift runtime is unavailable.

Instructions

Inspect Redshift materials with best-effort fallbacks.

This tool is read-only and is designed to be useful even when the Redshift
Python runtime is unavailable. It can still report names, assignments,
preview-derived colors, readable description/container fields, and will
attempt graph inspection only when Cinema 4D exposes that data.

Args:
    material_name: Optional material name filter
    include_assignments: Include texture-tag assignments in the scene
    include_preview: Include sampled preview bitmap color data
    include_description: Include readable description entries
    include_container: Include safe BaseContainer values
    include_graph: Attempt node-graph inspection when available

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
material_nameNo
include_assignmentsNo
include_previewNo
include_descriptionNo
include_containerNo
include_graphNo

Implementation Reference

  • The implementation of the `inspect_redshift_materials` tool handler. It establishes a connection to Cinema 4D, constructs a command dictionary, sends it, and returns the formatted JSON response.
    async def inspect_redshift_materials(
        material_name: Optional[str] = None,
        include_assignments: bool = True,
        include_preview: bool = True,
        include_description: bool = True,
        include_container: bool = True,
        include_graph: bool = True,
        ctx: Context = None,
    ) -> str:
        """
        Inspect Redshift materials with best-effort fallbacks.
    
        This tool is read-only and is designed to be useful even when the Redshift
        Python runtime is unavailable. It can still report names, assignments,
        preview-derived colors, readable description/container fields, and will
        attempt graph inspection only when Cinema 4D exposes that data.
    
        Args:
            material_name: Optional material name filter
            include_assignments: Include texture-tag assignments in the scene
            include_preview: Include sampled preview bitmap color data
            include_description: Include readable description entries
            include_container: Include safe BaseContainer values
            include_graph: Attempt node-graph inspection when available
        """
        async with c4d_connection_context() as connection:
            if not connection.connected:
                return "❌ Not connected to Cinema 4D"
    
            command = {
                "command": "inspect_redshift_materials",
                "include_assignments": include_assignments,
                "include_preview": include_preview,
                "include_description": include_description,
                "include_container": include_container,
                "include_graph": include_graph,
            }
    
            if material_name:
                command["material_name"] = material_name
    
            response = send_to_c4d(connection, command)
    
            if "error" in response:
                return f"❌ Error: {response['error']}"
    
            return json.dumps(response, indent=2)
  • Tool registration using the `@mcp.tool()` decorator for the `inspect_redshift_materials` function.
    @mcp.tool()
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by declaring it's read-only, works with fallbacks when runtime is unavailable, and specifies what data it can report (names, assignments, preview colors, etc.). It also notes graph inspection is only attempted when Cinema 4D exposes that data, adding useful behavioral context.

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 appropriately sized and front-loaded with the core purpose, followed by a structured parameter explanation. Every sentence adds value, though the parameter list is somewhat verbose but necessary given the lack of schema descriptions.

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

Completeness4/5

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

Given the complexity (6 parameters, no annotations, no output schema), the description is quite complete: it explains the tool's behavior, fallback mechanisms, and each parameter's semantics. It could improve by hinting at return values or error handling, but covers most essentials well.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate fully. It provides a detailed 'Args' section explaining each parameter's purpose (e.g., 'material_name' as an optional filter, 'include_assignments' for texture-tag assignments), adding significant meaning beyond the bare schema titles.

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 inspects Redshift materials with best-effort fallbacks, specifying it's read-only and works even when Redshift Python runtime is unavailable. It distinguishes from siblings like 'apply_material' or 'create_material' by focusing on inspection rather than creation or application, though it doesn't explicitly name alternatives.

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

Usage Guidelines3/5

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

The description implies usage when inspecting materials, especially in environments where Redshift Python runtime might be unavailable, but doesn't provide explicit guidance on when to use this versus alternatives like 'get_scene_info' or 'list_objects'. No exclusions or prerequisites are mentioned.

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