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") }] };
      }
    );
Behavior3/5

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

Since no annotations exist, description carries full burden. It discloses return structure (label, path, type, visibility) which compensates partially for missing output schema. However, it omits safety characteristics (read-only), error conditions, or performance traits.

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 of 10 words. Front-loaded with verb 'List', every word earns its place by describing both the action and the specific fields returned.

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 zero-parameter tool, the description is reasonably complete. It compensates for the missing output schema by enumerating the returned fields (label, path, type, visibility). Could be improved by noting the read-only/safe nature of the 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?

Input schema has zero parameters, establishing a baseline of 4. The description appropriately does not attempt to add parameter semantics where none exist.

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 ('List') and resource ('configured repos') clearly, including scope ('all'). However, it does not explicitly differentiate from siblings like get_config_info or check_repo_branch.

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?

Provides no guidance on when to use this tool versus alternatives like get_config_info or check_repo_branch. No prerequisites or conditions are mentioned.

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