Cinema4D MCP

Overview Schema Source Related Servers Discussions Admin

inspect_redshift_materials

Inspect Redshift materials in Cinema 4D scenes, reporting names, assignments, preview colors, descriptions, and node-graph data with fallbacks when the 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

Name	Required	Description	Default
`include_graph`	No
`material_name`	No
`include_preview`	No
`include_container`	No
`include_assignments`	No
`include_description`	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

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it discloses read-only semantics, best-effort fallbacks, partial functionality without the Redshift runtime, and conditional data availability for node-graph inspection. This is exactly the kind of behavioral transparency that helps an agent predict outcomes.

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

Conciseness5/5

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

The description is compact, front-loaded with the key purpose and fallback behavior, and then lists parameters in a scannable block. Every sentence carries useful information with no filler.

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

Completeness5/5

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

For a tool with six optional parameters and an output schema, the description covers the operation's limitations, read-only nature, and each parameter's intent. Nothing critical is missing for an agent deciding when and how to call it.

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%, but the Args block explains every parameter in plain terms: filter, include assignments, preview colors, descriptions, container values, and graph inspection. This adds real meaning beyond the bare schema titles and tells the agent what each flag controls.

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

Purpose5/5

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

The first sentence names the exact resource and action: 'Inspect Redshift materials', and the follow-up clarifies it is a read-only introspection tool. This cleanly separates it from sibling creation/application tools like create_material and apply_material.

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

Usage Guidelines4/5

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

The description states it is read-only, designed to work even when the Redshift Python runtime is unavailable, and that graph inspection only happens when Cinema 4D exposes that data. It gives clear context for when to use it, though it does not explicitly name alternative tools or exclusion cases.

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