Skip to main content
Glama
kumoproductions

mcp-cinema4d

by kumoproductions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set Layer Flags

set_layer_flags

Toggle a Cinema 4D layer's visibility, render, and lock flags in one call, modifying only specified fields and preserving others.

Instructions

Toggle a layer's visibility / render / lock flags in one call. Only fields explicitly passed are modified; omitted flags keep their current value. flags returned in the response reflects the post-update state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
soloNo
viewNo
xrefNo
colorNoOptional color update as [r,g,b] in 0..1.
layerYesLayer name (required).
lockedNo
renderNo
managerNo
animationNo
deformersNo
generatorsNo
expressionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.1
    • changedInput schema / properties / color / items
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "number"
-  }
-]New value: +{
+  "type": "number"
+}
    • addedInput schema / properties / color / maxItems
      Added value: +3
    • addedInput schema / properties / color / minItems
      Added value: +3
  2. First observedv0.3.1

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose a non-obvious, valuable trait: only explicitly passed fields are modified, so the tool is a safe partial mutation rather than a reset. It also states the response's `flags` reflects post-update state (useful with no output schema). It omits undo-ability, required context, and the meaning of the eight undocumented boolean flags.

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?

Three short sentences, front-loaded with the action, then the partial-update rule, then the return-value note. No hedging or filler; every sentence earns its place.

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

Completeness3/5

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

It covers the update semantics and the response shape well enough to call the tool correctly in broad strokes, and the absent output schema is partly compensated by the `flags` sentence. However, for a 12-parameter mutation tool with no annotations, the unexplained boolean flags leave a real gap in knowing what each parameter does.

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

Parameters2/5

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

Schema coverage is only 17% – just `layer` and `color` are documented. The description compensates by naming visibility/render/lock but never explains solo, view, xref, manager, animation, deformers, generators, or expressions, leaving most of the 12 parameters semantically opaque to an agent that must set them.

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 specific verb+resource+scope: toggling a layer's visibility/render/lock flags in a single call. An agent can distinguish it from list_layers or get_object_layer. It stops short of 5 because it names only three of the many boolean flags the tool actually accepts, so the tool's full purpose is narrower in prose than in schema.

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 phrase 'in one call' implies batch-style use versus repeated single-flag updates, and the note that omitted flags keep their current value guides partial updates. But no explicit when-to-use/when-not guidance relative to siblings like get_object_layer or set_params, so usage is only implied.

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

Deploy Server

Other Tools