Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

get_config_info

Retrieve the configuration file path and current settings for the Claude git repository monitoring plugin.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'get_config_info' MCP tool, which returns the path to the config file and the full current configuration.
    // --- 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)}` },
          ],
        };
      }
    );
  • Registration of the 'get_config_info' tool within the registerConfigTools function.
    // --- 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It specifies the return content (path and configuration), implying a read-only operation, but fails to explicitly state safety characteristics, side effects, or whether the configuration might be sensitive/large.

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 sentence of 11 words with no redundant content. The information is front-loaded with the verb 'Return' immediately clarifying the tool's action.

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 the tool's simplicity (zero parameters) and lack of output schema, the description adequately compensates by specifying what data is returned. However, it could improve by indicating the configuration format (JSON, YAML, etc.) or structure.

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 has zero parameters with 100% coverage, establishing the baseline score of 4. No additional parameter semantics are needed or provided in the description.

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 full configuration, distinguishing it from sibling repository management tools (add_repo, list_repos, etc.). However, it lacks specificity about what 'configuration' encompasses (global settings vs. repo-specific settings).

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 any prerequisites or context. While it's a simple getter with no parameters, explicit guidance on when inspection is appropriate would help agent selection.

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