Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_collection_visibility

Set a Blender collection's visibility for viewport and/or render by providing the collection name and desired visible state.

Instructions

Set collection visibility in viewport and/or render.

Args: collection_name: Name of the collection. visible: Whether the collection should be visible. viewport: Apply visibility change to viewport. Defaults to True. render: Apply visibility change to render. Defaults to True.

Returns: Confirmation dict with visibility state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
renderNo
visibleYes
viewportNo
collection_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • addedInput schema / properties / collection_name
      Added value: +{
+  "title": "Collection Name",
+  "type": "string"
+}
    • removedInput schema / properties / name
      Removed value: -{
-  "title": "Name",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "visible"
-]New value: +[
+  "collection_name",
+  "visible"
+]
  2. Changed1 schema field changedv1.2.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "set_collection_visibilityDictOutput",
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the behavioral scope (affects viewport and/or render independently) and states the return value, but says nothing about whether the collection must already exist, whether the change is reversible, or any error conditions for this mutation.

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 leading sentence is front-loaded and states the core purpose. The Args/Returns block is slightly padded and partly duplicates the schema (notably the defaults), but it is readable and not wasteful overall.

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?

For a 4-parameter mutation with no annotations, the description documents every parameter and the effect scope, which is the key information. The Returns line is redundant given the output schema exists, and error behavior is unaddressed, but nothing essential for calling the tool is missing.

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

Parameters4/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, and it does: all four parameters are explained, including the default-true semantics of viewport and render. Only a minor gap remains, such as whether collection_name must be an exact name.

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?

States a specific verb and resource ('Set collection visibility') and scopes it precisely to 'viewport and/or render'. This is clearly distinguishable from sibling tools such as set_object_visibility, since the resource (collection) is named explicitly.

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 through the viewport/render scope flags, which tells the agent it can target either mode, but it offers no explicit when-to-use guidance and never mentions alternatives (set_object_visibility, move_to_collection). Usage is inferable but not stated.

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