Skip to main content
Glama
Sign In
GitPilot MCP

GitPilot MCP

by Divyanshu-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

index_repo

Indexes a repository for semantic code search, storing the index in a centralized location to keep the repository clean.

Instructions

Index a repository for semantic code search.

The index is stored in a centralized location to avoid polluting the repository with .rag folders.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo_path": "<repo_path>"
    },
    "name": "index_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_pathYesAbsolute path to the repository to index

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations are absent, so description carries burden. It reveals storage location and non-pollution of repo, but doesn't discuss idempotency, overwriting, or side effects. Adequate but not comprehensive.

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?

Two sentences with no wasted words. Purpose is front-loaded, and storage note is concise and relevant.

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?

Tool is simple with one parameter and output schema exists. Description covers key points for usage and storage. Missing minor details like return value but overall complete.

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% with one parameter described as 'Absolute path to the repository to index'. Description adds no extra meaning about format or constraints, meeting baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Index a repository for semantic code search' with a specific verb and resource. It distinguishes from siblings like 'reindex_repository' and 'list_indexed_repositories' by focusing on the initial indexing action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies when to use (initial index) but lacks explicit guidance on alternatives like 'reindex_repository' or when not to use. No exclusions or context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools