Skip to main content
Glama
onesmartguy

Agentic Bits Claude Plugin

by onesmartguy

toggle_reference_repos

Control visibility of reference repositories in the status bar to focus on active projects 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

  • Handler implementation for toggle_reference_repos tool which updates the statusbar.showReferenceRepos configuration value.
    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?

No annotations provided, so description carries full disclosure burden. Explains the visibility toggle behavior but omits persistence details (session vs permanent), side effects on other tools, or definition of 'reference' vs 'active' repo types. No contradictions present.

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 efficient sentence with zero waste. Action verb front-loaded, scope clearly delimited by 'in the status bar.' Appropriate length for tool complexity.

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?

Adequate for a simple 1-parameter toggle tool. Status bar context is specified. No output schema exists, but return value is likely implicit boolean success; description doesn't need to elaborate for this complexity level.

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% (parameter 'show' fully documented). Description does not add parameter-level semantics beyond schema, which is acceptable baseline when schema is complete.

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 specific action (show/hide), target resource (repos type 'reference'), and location (status bar). Implicitly distinguishes from sibling toggle_statusbar by specifying it's for filtering repo types rather than the status bar itself.

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?

No explicit when-to-use guidance or contrast with siblings like toggle_statusbar (which likely controls the entire status bar visibility) versus this tool which filters content within it. Uses must infer applicability from the action description alone.

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