Skip to main content
Glama

Visibility Set

visibility_set
Destructive

Sets a component or page to show only when a report or datasource variable is true, or removes the rule. Includes dry-run preview and fingerprint conflict checks.

Instructions

Control visibility: show a component (or the page when component_id is omitted) only when a variable is true / the viewer is in its group. source_key is "REPORT_VARIABLE:" or "DATASOURCE_VARIABLE::"; null removes the rule. page_get fingerprint; journalled and restorable.

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": {
      "page_id": "<page_id>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "visibility_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
page_idYes
report_idNo
source_keyNo
component_idNo
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, so the mutation risk is already signalled. The description adds genuinely useful context beyond that (null deletes the rule, the write is journalled and restorable, and an expected_fingerprint guard applies). However, it never explains the default dry_run=true behaviour or what a rejected fingerprint does, leaving the primary safety mechanism under-described.

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 purpose is front-loaded and the whole definition is two dense sentences with no filler. The telegraphic closing fragment ('page_get fingerprint; journalled and restorable') is compact but slightly cryptic, costing a little clarity.

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 destructive, fingerprint-guarded mutation tool this covers the essentials: what is targeted, the source_key syntax, removal semantics, and reversibility. An output schema exists so return values need no explanation, but the unexplained dry_run default and report_id leave a small gap for a 6-parameter tool.

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 0%, so the description must carry parameter meaning, and it only partly does. It explains component_id scoping, source_key's two literal formats, null-removal, and the fingerprint link to page_get, but says nothing about report_id or dry_run, leaving two of six parameters undocumented anywhere.

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 description states a specific verb and resource ('Control visibility') and defines scope precisely: it targets a component, or the whole page when component_id is omitted. That scope rule alone separates it from the sibling control_*_set tools, which mutate report controls rather than visibility rules.

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

Usage Guidelines4/5

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

It gives clear operational context: the rule is conditional on a variable/group, and passing null removes the rule. It also implicitly points at page_get for the fingerprint. It stops short of naming alternatives or stating when not to use it (e.g. vs control_parameter_set), so it is not a full 5.

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