Skip to main content
Glama

Set Visibility

set_visibility
Destructive

Override an object's persistent visibility flag so hidden producer-inputs or reference primitives stay visible; pair with save_document visibility_hygiene=False to lock the override.

Instructions

Override an object's persistent Visibility flag. By default save_document auto-hides producer-inputs (the Base/Tool of a Cut, features inside a Body) so the re-opened doc shows just the final composition. Use this to override — e.g. to keep a reference primitive visible next to a derived part. Note that the next save_document with visibility_hygiene=True (the default) may re-hide it; pass visibility_hygiene=False to save_document to lock the override in.

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

Input Schema

NameRequiredDescriptionDefault
handleYes
visibleYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the generic destructive/not-read-only profile; the description adds genuinely new behavioral facts: the override is persistent, it can be silently undone by the next hygiene-enabled save, and how to lock it in. It does not state whether the flag applies to sub-features recursively or what happens to objects already hidden, but overall it carries far more than the annotations.

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-loads the purpose, then the default it overrides, then the caveat about re-hiding — a logical order with little waste. The parenthetical example is helpful rather than filler, though the final sentence is a bit dense.

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?

No output schema exists, so the description should cover the outcome; it explains persistence and the save-time interaction, which is the main thing an agent could get wrong. The remaining gap is handle semantics and scope of the visibility change, which the schema does not fill either.

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

Parameters3/5

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

Schema coverage is only 33%: workspace is documented, but handle and visible are bare. The description implies handle identifies 'an object' and that visible toggles the flag, which is mild compensation, but there is no explanation of handle format/resolution or what setting visible=false does to descendants.

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 (override) and resource (an object's persistent Visibility flag), and immediately distinguishes the tool from save_document's default auto-hide behavior. An agent can tell what this does and how it differs from the save-time hygiene policy without opening the schema.

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?

Explicitly describes the default behavior it overrides (save_document auto-hides producer-inputs), gives a concrete use case (keeping a reference primitive visible next to a derived part), and explains the escape hatch (pass visibility_hygiene=False to save_document). This is unusually complete routing guidance.

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