Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

toggle_statusbar

Enable or disable the Claude interface status bar to control visibility of live git repository monitoring information.

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 handler implementation for the toggle_statusbar tool, which updates the configuration's statusbar.enabled setting.
    // --- 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?

No annotations provided, so description carries full burden. Adds valuable behavioral context beyond the schema by explaining the consequence of disabling (status line script outputs nothing). However, lacks details on persistence (session vs permanent), scope (user vs system-wide), or idempotency that would fully characterize the tool's behavior.

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?

Two sentences with zero waste. Front-loaded with the core action ('Enable or disable the entire status bar') followed immediately by behavioral consequence. Every word earns its place; no redundancy with schema or name.

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 functionality and immediate side effects. For a basic toggle tool, explaining the disabled state behavior is sufficient, though additional context about persistence or integration with other status-related tools would be ideal.

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 100% with clear parameter description ('true = enable, false = disable'). The description references 'Enable or disable' which aligns with the parameter semantics, but doesn't add syntax details, examples, or validation rules beyond what the schema already provides. Baseline 3 is appropriate given complete schema coverage.

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?

States specific action (enable/disable) on specific resource (entire status bar). Implicitly distinguishes from repo-focused siblings (add_repo, list_repos, etc.) by addressing UI configuration rather than repository management, though it doesn't explicitly clarify the distinction from sibling `toggle_reference_repos`.

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

Usage Guidelines3/5

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

Provides implicit usage guidance through behavioral description ('When disabled the status line script outputs nothing'), helping the agent understand the effect of disabling. However, lacks explicit 'when to use' criteria, prerequisites, or comparison to alternatives like `toggle_reference_repos`.

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