Skip to main content
Glama

set_visibility

Show or hide a USD prim and everything under it in the viewport and captures while keeping the prim in the stage. Use it to see inside or behind objects, then show again.

Instructions

Show or hide a prim and everything under it, in the viewport and in captures; the prim stays in the stage.

Use it to see inside or behind something, then show it again; delete_prim removes a prim, and inspect_prim's isolate hides all but one prim for its captures. Showing a prim under a hidden parent shows the parent and hides the parent's other children, as USD's MakeVisible does. An error for a prim that has no visibility, such as a material.

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": {
      "prim_path": "<prim_path>"
    },
    "name": "set_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
visibleNoTrue to show, False to hide
prim_pathYesFull USD path of the prim, e.g. "/World/Robot"

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare non-read-only but non-destructive, and the description substantiates that by stating the prim persists in the stage. It goes further than annotations can by disclosing the hierarchical MakeVisible cascade (shows the hidden parent, hides the parent's other children) and the error case for prims with no visibility, such as materials.

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?

Front-loaded with the action and scope, then alternatives, then edge-case semantics in descending priority. It is dense with three clauses carrying distinct information, but nothing reads as filler; a slightly tighter phrasing of the MakeVisible analogy would be the only trim.

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 mutating visibility tool with an output schema, the description covers what changes, what does not change (the prim remains), the inheritance behavior, the alternative tools, and the failure mode. Nothing an agent needs in order to call it correctly or interpret failure 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 coverage is 100%, so both parameters are already documented; the description still adds meaning by implying the boolean toggles a subtree rather than a single node. It could have noted the default of true explicitly in prose, which is the only small gap.

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 opening clause names a specific verb ("Show or hide") and resource ("a prim and everything under it") and scopes the effect to viewport and captures while clarifying that the prim stays in the stage. This clearly separates it from delete_prim (removal) and inspect_prim's isolate (capture-only hiding), both named siblings.

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

Usage Guidelines5/5

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

Explicit when-to-use ("to see inside or behind something, then show it again") plus explicit differentiation from the two most confusable alternatives, delete_prim and inspect_prim's isolate. The parent/child cascade rule tells the agent the precondition and side effects of the call before it runs.

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