Skip to main content
Glama
onesmartguy

Agentic Bits Claude Plugin

by onesmartguy

get_config_info

Retrieve the configuration file path and current settings for the Agentic Bits Claude Plugin's git repository tracking system.

Instructions

Return the path to the config file and the full current configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the get_config_info tool, which retrieves and returns the current configuration and its file path.
    server.tool(
      "get_config_info",
      "Return the path to the config file and the full current configuration.",
      {},
      async () => {
        const config = loadConfig();
        return {
          content: [
            { type: "text", text: `Config file: ${configPath()}\n\n${JSON.stringify(config, null, 2)}` },
          ],
        };
      }
    );
  • The tool is registered within the registerConfigTools function.
    export function registerConfigTools(server: McpServer): void {
      // --- list_repos ---
      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") }] };
        }
      );
    
      // --- add_repo ---
      server.tool(
        "add_repo",
        "Add a repository to the status bar. The path must be an absolute filesystem path to a git repo root.",
        {
          path: z.string().describe("Absolute path to the git repo"),
          label: z.string().describe("Short display label, e.g. 'payment-service'"),
          type: z.enum(["active", "reference"]).default("active").describe("'active' for dev repos, 'reference' for read-only refs"),
          show: z.boolean().default(true).describe("Whether to show this repo in the status bar immediately"),
        },
        async ({ path, label, type, show }) => {
          const config = loadConfig();
          const exists = config.repos.find((r) => r.path === path || r.label === label);
          if (exists) {
            return { content: [{ type: "text", text: `Repo already configured: ${exists.label} (${exists.path}). Use set_repo_visibility or remove_repo first.` }] };
          }
          if (!isGitRepo(path)) {
            return { content: [{ type: "text", text: `Warning: "${path}" does not appear to be a git repo. Added anyway — verify the path is correct.` }] };
          }
          const repo: RepoConfig = { path, label, type, show };
          config.repos.push(repo);
          saveConfig(config);
          return { content: [{ type: "text", text: `Added repo: ${label} (${path}) [${type}, ${show ? "visible" : "hidden"}]` }] };
        }
      );
    
      // --- 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}` }] };
        }
      );
    
      // --- set_repo_visibility ---
      server.tool(
        "set_repo_visibility",
        "Show or hide a specific repo in the status bar by its label.",
        {
          label: z.string().describe("Repo label"),
          show: z.boolean().describe("true = show in status bar, false = hide"),
        },
        async ({ label, show }) => {
          const config = loadConfig();
          const repo = config.repos.find((r) => r.label === label);
          if (!repo) {
            return { content: [{ type: "text", text: `No repo found with label "${label}".` }] };
          }
          repo.show = show;
          saveConfig(config);
          return { content: [{ type: "text", text: `${label}: now ${show ? "visible" : "hidden"} in status bar.` }] };
        }
      );
    
      // --- toggle_statusbar ---
      server.tool(
        "toggle_statusbar",
        "Enable or disable the entire status bar. When disabled the status line script outputs nothing.",
        { enabled: z.boolean().describe("true = enable, false = disable") },
        async ({ enabled }) => {
          const config = loadConfig();
          config.statusbar.enabled = enabled;
          saveConfig(config);
          return { content: [{ type: "text", text: `Status bar ${enabled ? "enabled" : "disabled"}.` }] };
        }
      );
    
      // --- toggle_reference_repos ---
      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.` }] };
        }
      );
    
      // --- get_config_info ---
      server.tool(
        "get_config_info",
        "Return the path to the config file and the full current configuration.",
        {},
        async () => {
          const config = loadConfig();
          return {
            content: [
              { type: "text", text: `Config file: ${configPath()}\n\n${JSON.stringify(config, null, 2)}` },
            ],
          };
        }
      );
    }
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It specifies that two distinct values are returned (file path and configuration content), but omits safety details, error conditions (e.g., missing config file), or whether this reads from disk potentially impacting performance.

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?

The description is a single, efficient 12-word sentence with the action verb ('Return') front-loaded. No words are wasted, and the length is appropriate for a parameter-less utility function.

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 no output schema exists, the description appropriately explains what is returned (path and configuration). It adequately covers the tool's simplicity, though it could enhance completeness by mentioning the config format or error scenarios.

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?

The input schema contains zero parameters, which per the guidelines establishes a baseline score of 4. The description correctly implies no inputs are needed by focusing entirely on return values.

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 tool returns the config file path and current configuration using specific verbs and resources. While it doesn't explicitly contrast with the repo-focused siblings (add_repo, list_repos, etc.), the name and description make the distinct purpose evident.

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 mention prerequisites such as whether a configuration must exist first or how this relates to the repo management sibling tools.

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