Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

list_repos

Display all tracked repositories with their label, path, type, and visibility status to monitor multiple git projects simultaneously.

Instructions

List all configured repos with their label, path, type, and visibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the list_repos tool handler.
    server.tool(
      "list_repos",
      "List all configured repos with their label, path, type, and visibility.",
      {},
      async () => {
        const config = loadConfig();
        if (config.repos.length === 0) {
          return { content: [{ type: "text", text: "No repos configured. Use add_repo to add one." }] };
        }
        const lines = config.repos.map((r) => {
          const vis = r.show ? "visible" : "hidden";
          return `[${vis}] ${r.label} (${r.type})\n  path: ${r.path}`;
        });
        const header = [
          `Status bar: ${config.statusbar.enabled ? "ON" : "OFF"}`,
          `Show reference repos: ${config.statusbar.showReferenceRepos ? "yes" : "no"}`,
          "",
        ].join("\n");
        return { content: [{ type: "text", text: header + lines.join("\n\n") }] };
      }
    );

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses output structure by listing specific fields returned (label, path, type, visibility). However, omits safety confirmation (though implied by 'List'), auth requirements, or performance characteristics.

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, perfectly front-loaded. Action verb leads, followed by scope and output specification. No redundancy or filler.

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 zero parameters and no output schema, the description adequately compensates by enumerating the output fields. Could improve by specifying return format (array/object) or noting this retrieves local configuration only.

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?

Zero parameters required. Schema is empty object as expected. Baseline score applies.

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?

Specific verb 'List' + resource 'configured repos' + scope 'all'. Field enumeration (label, path, type, visibility) distinguishes from sibling tools like get_config_info (general settings) and check_repo_branch (specific repo operations).

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?

Implied usage as an inventory/catalog operation by specifying output fields, but lacks explicit guidance on when to use versus get_config_info or prerequisites for calling this before repo-specific operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.