Skip to main content
Glama
onesmartguy

Agentic Bits Claude Plugin

by onesmartguy

set_repo_visibility

Control repository visibility in the status bar by showing or hiding specific repositories using their labels.

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 implementation of the `set_repo_visibility` tool, which updates the `show` property 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.` }] };
      }
    );
Behavior3/5

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

With no annotations, the description must carry full behavioral disclosure. It successfully identifies the UI location ('status bar') which is critical context, but omits persistence behavior (does this setting survive restart?), error handling for invalid labels, or whether this affects other views beyond the status bar.

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?

Single 11-word sentence with zero redundancy. Front-loaded with the action ('Show or hide'), followed by target ('specific repo'), location ('status bar'), and key parameter ('by its label'). Every word 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?

Adequate for a simple 2-parameter toggle with no output schema. Captures the essential operation and UI context. However, lacks completeness regarding error conditions (invalid label) and relationship to the registration state of the repo (managed by sibling 'add_repo').

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 has 100% description coverage ('Repo label' and boolean semantics). The description mirrors this information ('Show or hide' aligns with the boolean, 'by its label' references the string param) but adds no additional syntax guidance, constraints, or examples beyond what the schema already provides. Baseline 3 appropriate for high-coverage schemas.

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?

Clear verb pair ('Show or hide') with specific resource ('repo') and scope ('in the status bar'). The 'by its label' qualifier maps to the required parameter. Distinguishes from sibling 'toggle_statusbar' (which implies global UI toggle) by specifying 'specific repo', though it doesn't explicitly reference the visibility concept from the tool name.

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?

Provides no guidance on when to use this versus 'toggle_statusbar' or 'toggle_reference_repos', nor does it state prerequisites like the repo needing to exist first (implied by 'label' reference). No mention of when showing/hiding is appropriate.

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/onesmartguy/agentic-bits-claude-plugin'

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