Skip to main content
Glama

set_object_visibility

Control visibility flags for a Blender object by name, including hide render, hide select, and hide viewport settings. Use it to show or hide objects in renders, selection, or the viewport.

Instructions

Set object visibility flags.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "set_object_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
hide_renderNo
hide_selectNo
hide_viewportNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it discloses almost nothing: it does not state whether omitting a flag leaves the current visibility untouched, whether the change is reversible or persisted, or whether it requires a specific context (viewport vs. render). Only the bare fact that visibility settings are mutated is conveyed.

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?

A single short, front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of substance rather than being a virtue of tight editing.

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?

An output schema exists, so return values needn't be described, but for a four-parameter mutation tool with no annotations and zero schema coverage, the definition omits nearly everything an agent needs to call it correctly.

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 description coverage is 0%, so the description must compensate and does not. It never explains that name identifies the target object or that the hide_* parameters are nullable booleans where null likely means "leave unchanged" — the only hint is the generic word "flags".

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

Purpose3/5

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

The description gives a verb and resource ("Set object visibility flags") but "flags" is unspecified — an agent can't tell from the text that the flags are hide_render, hide_select, and hide_viewport, nor how this differs from siblings such as modify_object or set_object_shading.

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?

No guidance on when to use this versus modify_object or other set_object_* tools, and no mention of prerequisites such as an active/selected object or whether the object must exist. The agent must infer usage entirely from the tool name.

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