Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

set_repo_visibility

Control repository visibility in the status bar by showing or hiding specific repos using their labels to manage monitoring focus.

Instructions

Show or hide a specific repo in the status bar by its label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesRepo label
showYestrue = show in status bar, false = hide

Implementation Reference

  • The handler implementation for the set_repo_visibility tool, which updates the visibility of a repository in the configuration and saves the changes.
    // --- set_repo_visibility ---
    server.tool(
      "set_repo_visibility",
      "Show or hide a specific repo in the status bar by its label.",
      {
        label: z.string().describe("Repo label"),
        show: z.boolean().describe("true = show in status bar, false = hide"),
      },
      async ({ label, show }) => {
        const config = loadConfig();
        const repo = config.repos.find((r) => r.label === label);
        if (!repo) {
          return { content: [{ type: "text", text: `No repo found with label "${label}".` }] };
        }
        repo.show = show;
        saveConfig(config);
        return { content: [{ type: "text", text: `${label}: now ${show ? "visible" : "hidden"} in status bar.` }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. While it states the immediate action, it omits behavioral traits such as whether changes persist across sessions, what happens if the label doesn't exist, or required permissions. For a state-mutation tool, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient 11-word sentence. It front-loads the action verbs and wastes no words. Every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 parameters, 100% schema coverage, no output schema), the description is minimally adequate. However, for a mutation operation with zero annotations, it should disclose error conditions or persistence behavior to be complete.

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 description coverage is 100%, with 'label' described as 'Repo label' and 'show' as 'true = show in status bar, false = hide'. The description mirrors this information ('by its label', 'Show or hide') but adds no additional semantic context like label format requirements or default behaviors.

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

Purpose4/5

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

The description uses specific verbs ('Show or hide') and identifies the resource ('specific repo') and scope ('in the status bar'). It implicitly distinguishes from sibling 'toggle_statusbar' by focusing on a specific repo rather than the entire status bar, though it could explicitly mention this distinction.

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?

The description provides no explicit guidance on when to use this tool versus siblings like 'toggle_statusbar' or 'list_repos'. It lacks 'when-to-use' or 'when-not-to-use' criteria, forcing the agent to infer appropriate usage solely from the function name.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agenticbits/claude-plugin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server