Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

toggle_reference_repos

Control visibility of reference repositories in the status bar to focus on active repositories or include reference materials as needed.

Instructions

Show or hide repos marked as type 'reference' in the status bar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
showYestrue = include reference repos, false = active repos only

Implementation Reference

  • The handler for the 'toggle_reference_repos' tool, which updates the configuration and saves it.
    server.tool(
      "toggle_reference_repos",
      "Show or hide repos marked as type 'reference' in the status bar.",
      { show: z.boolean().describe("true = include reference repos, false = active repos only") },
      async ({ show }) => {
        const config = loadConfig();
        config.statusbar.showReferenceRepos = show;
        saveConfig(config);
        return { content: [{ type: "text", text: `Reference repos: ${show ? "shown" : "hidden"} in status bar.` }] };
      }
    );
  • Registration of the 'toggle_reference_repos' tool within the McpServer instance.
    server.tool(
      "toggle_reference_repos",
      "Show or hide repos marked as type 'reference' in the status bar.",
      { show: z.boolean().describe("true = include reference repos, false = active repos only") },
      async ({ show }) => {
        const config = loadConfig();
        config.statusbar.showReferenceRepos = show;
        saveConfig(config);
        return { content: [{ type: "text", text: `Reference repos: ${show ? "shown" : "hidden"} in status bar.` }] };
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden. It identifies the UI component affected (status bar) but omits critical behavioral details: whether the setting persists across sessions, if it affects other users/workspace members, or what the operation returns. The 'Show or hide' phrasing slightly conflicts with the imperative name 'toggle' and boolean parameter 'show', though this is minor.

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?

Extremely efficient at 11 words. The single sentence front-loads the action verbs and every word earns its place. No redundancy or boilerplate.

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 single-parameter configuration tool without output schema, the description covers the essential functionality. Minor gaps remain regarding persistence and side effects, but given the low complexity, the description is sufficiently complete for agent operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, establishing a baseline of 3. The description adds value by defining 'reference' repos and connecting the parameter to the status bar context. The schema's parameter description ('true = include reference repos, false = active repos only') clarifies the boolean semantics, and the main description reinforces this by specifying repos 'marked as type reference'.

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 clearly states the specific action (show/hide), target resource (repos of type 'reference'), and location/context (status bar). It effectively distinguishes from sibling 'toggle_statusbar' (which likely controls the entire bar) and 'list_repos' (which retrieves data rather than configuring display).

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?

The description implies usage through the reference vs. active repo distinction (mirrored in the parameter description), but provides no explicit when-to-use guidance, prerequisites, or comparison to alternatives like 'list_repos'. Agents must infer when this display configuration 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/agenticbits/claude-plugin'

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