Skip to main content
Glama
onesmartguy

Agentic Bits Claude Plugin

by onesmartguy

validate_repo_path

Verify if a filesystem path exists and contains a valid git repository. Use this tool to confirm repository paths before performing git operations.

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 implementation for the `validate_repo_path` tool, which checks if a path exists and is a git repository.
    // --- 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}` }] };
      }
    );
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. While it specifies the dual validation logic (existence + git status), it omits critical behavioral traits: read-only nature, return value structure (boolean vs object), error behavior on invalid paths, and side effects.

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 structure with zero redundancy. Front-loaded with action verb. Every word earns its place. Appropriate length for tool complexity.

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 simple single-parameter tool with complete schema coverage, though gaps remain due to missing output schema (no indication of success/failure return format or error conditions) and zero annotations providing context.

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 has 100% coverage ('Absolute path to check'). Description references 'filesystem path' but adds no semantic elaboration (e.g., format constraints, relative vs absolute path handling, examples) beyond the schema baseline. Baseline 3 warranted by high schema coverage.

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?

Clear action verb 'Check' and specific validation targets (path existence AND git repository status). Resource scope is explicit ('filesystem path'). Distinction from siblings like 'check_repo_branch' is conceptually clear (path validation vs branch inspection) though not explicitly stated.

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?

States what the tool validates but provides no guidance on when to invoke it versus alternatives (e.g., 'use before add_repo to verify', 'do not use for already registered repos—use list_repos instead'). No preconditions or exclusions 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/onesmartguy/agentic-bits-claude-plugin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server