Skip to main content
Glama
onesmartguy

Agentic Bits Claude Plugin

by onesmartguy

toggle_statusbar

Control visibility of the git branch status bar in Claude's interface to manage repository tracking display.

Instructions

Enable or disable the entire status bar. When disabled the status line script outputs nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledYestrue = enable, false = disable

Implementation Reference

  • The implementation of the toggle_statusbar tool, which updates the statusbar.enabled configuration property and saves the configuration.
    // --- toggle_statusbar ---
    server.tool(
      "toggle_statusbar",
      "Enable or disable the entire status bar. When disabled the status line script outputs nothing.",
      { enabled: z.boolean().describe("true = enable, false = disable") },
      async ({ enabled }) => {
        const config = loadConfig();
        config.statusbar.enabled = enabled;
        saveConfig(config);
        return { content: [{ type: "text", text: `Status bar ${enabled ? "enabled" : "disabled"}.` }] };
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It successfully explains that disabled state causes the status line script to output nothing, but fails to describe the enabled state behavior, persistence, or any side effects.

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 consists of two efficient sentences with no waste. The primary action is front-loaded in the first sentence, while the second sentence provides immediate behavioral context, making it well-structured.

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?

Given the tool's simplicity (single boolean parameter, no output schema), the description adequately covers the essential functionality and immediate behavioral effect. It appropriately scopes the explanation to the tool's limited surface area.

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?

With 100% schema description coverage, the baseline is 3. The description mentions 'enable or disable' which aligns with the boolean 'enabled' parameter, but adds no additional semantic detail about the parameter's usage beyond what the schema already provides.

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 clearly states the tool enables or disables the status bar using specific verbs. While it distinguishes itself from repository-focused siblings, it lacks domain context about what the 'status bar' refers to (e.g., IDE, terminal, or repository status display).

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 alternatives, nor any prerequisites. It explains the behavioral consequence of disabling (no output) but does not frame this as usage guidance.

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