Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

remove_repo

Remove a repository from the status bar by specifying its label to declutter the interface and manage tracked repositories.

Instructions

Remove a repository from the status bar by its label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesRepo label to remove

Implementation Reference

  • The 'remove_repo' tool handler logic which removes a repository from the configuration based on its label.
    // --- remove_repo ---
    server.tool(
      "remove_repo",
      "Remove a repository from the status bar by its label.",
      { label: z.string().describe("Repo label to remove") },
      async ({ label }) => {
        const config = loadConfig();
        const before = config.repos.length;
        config.repos = config.repos.filter((r) => r.label !== label);
        if (config.repos.length === before) {
          return { content: [{ type: "text", text: `No repo found with label "${label}".` }] };
        }
        saveConfig(config);
        return { content: [{ type: "text", text: `Removed repo: ${label}` }] };
      }
    );
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 hints at safety by specifying 'from the status bar,' implying a UI-only operation, but fails to explicitly confirm this is non-destructive or reversible via add_repo. Lacks disclosure on side effects or failure modes.

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 sentence, front-loaded with the verb, zero redundancy. Every word earns its place given the tool's simplicity.

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 single-parameter tool with no output schema, but incomplete given the potential for user confusion between 'removing from UI' and 'deleting repository.' Should explicitly confirm the scope limitation for full completeness.

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 ('Repo label to remove'), the baseline is 3. The description mentions 'by its label,' aligning with the schema, but adds no additional semantic context such as valid label formats, case sensitivity, or where to find available labels (e.g., via list_repos).

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 action (Remove), resource (repository), and specific scope (from the status bar). It distinguishes itself from siblings like validate_repo_path or add_repo by specifying the status bar context, though it could explicitly clarify it is the inverse of add_repo.

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 guidance on when to use this tool versus alternatives, nor does it explicitly state that it does not delete the actual repository files (only removes from display). No mention of prerequisites or relationship to add_repo.

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