Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

validate_repo_path

Verify if a filesystem path exists and contains a valid git repository to ensure proper repository tracking and monitoring.

Instructions

Check whether a given filesystem path exists and is a git repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to check

Implementation Reference

  • The handler for 'validate_repo_path' checks if a path exists and is a valid git repository using 'existsSync' and 'isGitRepo'.
    // --- validate_repo_path ---
    server.tool(
      "validate_repo_path",
      "Check whether a given filesystem path exists and is a git repository.",
      { path: z.string().describe("Absolute path to check") },
      async ({ path }) => {
        if (!existsSync(path)) {
          return { content: [{ type: "text", text: `Path does not exist: ${path}` }] };
        }
        if (!isGitRepo(path)) {
          return { content: [{ type: "text", text: `Path exists but is not a git repo (no .git directory): ${path}` }] };
        }
        return { content: [{ type: "text", text: `Valid git repository: ${path}` }] };
      }
    );
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 clarifies the dual validation logic (existence + git-ness) but omits return value structure, error handling behavior, and explicit read-only safety guarantees that would be critical given destructive siblings like remove_repo.

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 with no redundancy, front-loaded with the action ('Check') and target ('filesystem path'). Every word serves the definition without filler.

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, but gaps remain regarding output format (boolean vs. object) and failure modes given the absence of an output schema or annotations.

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?

Schema coverage is 100% (path described as 'Absolute path to check'), establishing the baseline. The description mentions 'filesystem path' but adds no additional semantic constraints (e.g., symlink handling, required permissions) beyond what the schema already provides.

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 validates both filesystem existence and git repository status, distinguishing it from siblings like check_repo_branch (which validates branch state) and list_repos (which lists managed repositories).

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?

No explicit guidance on when to use this versus alternatives (e.g., list_repos for known managed repos) or prerequisites (e.g., path accessibility). The agent must infer usage context solely from the name and description.

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