kubesearch-mcp

Clone a repository (temporary)

repo_clone

Clone a public Git repository temporarily to inspect its files. Provide an indexed repo name or full HTTPS URL; receive a sandboxed clone, file tree, and handle for file operations.

Instructions

Temporarily clone a public Git repository so you can review its actual files. Accepts an indexed home-ops repo name (e.g. 'onedr0p/home-ops' — resolved to its real clone URL and branch) or a full https Git URL. The clone is shallow, sandboxed, size/time-limited, and auto-deleted after a TTL. Returns a handle to use with repo_list_files, repo_read_file, and repo_grep, plus a curated file tree to get you started. Call repo_cleanup when done.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`repo`	Yes	An indexed repo name like 'onedr0p/home-ops', or a full https:// Git URL.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tree`	Yes
`branch`	Yes
`handle`	Yes
`pinned`	Yes
`reused`	Yes
`size_mb`	Yes
`updated`	Yes
`file_count`	Yes
`resolved_url`	Yes
`expires_in_minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.2.0Sep 15, 2026

addedOutput schema / properties / pinned
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "handle",
-  "resolved_url",
-  "branch",
-  "file_count",
-  "size_mb",
-  "expires_in_minutes",
-  "reused",
-  "updated",
-  "tree"
-]New value: +[
+  "handle",
+  "resolved_url",
+  "branch",
+  "file_count",
+  "size_mb",
+  "expires_in_minutes",
+  "reused",
+  "updated",
+  "pinned",
+  "tree"
+]

First observedv0.1.0Aug 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description discloses substantial behavioral details beyond the annotations: the clone is shallow, sandboxed, size/time-limited, auto-deleted after a TTL, resolves indexed names to real clone URLs and branches, and requires eventual cleanup. This is exactly the kind of context an agent needs for a stateful, non-read-only operation.

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 front-loaded with the core purpose, then adds precise operational details in compact sentences. Every sentence earns its place, covering input format, clone behavior, return value, companion functions, and cleanup without filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete for a tool with one parameter, meaningful annotations, and an output schema. It explains what the caller receives, how the temporary resource is governed, and what follow-up actions are expected. Nothing essential for correct invocation is missing.

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?

With 100% schema description coverage, the schema already documents the `repo` parameter, and the description adds meaningful extra context: it gives an example, explains that indexed names are resolved to the real clone URL and branch, and states which URL forms are accepted. This goes beyond the schema without being redundant.

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?

The description uses a specific verb and resource: temporarily clone a public Git repository to review actual files. It clearly distinguishes itself from siblings by explaining that it returns a handle consumed by repo_list_files, repo_read_file, and repo_grep, and that repo_cleanup should be called afterward.

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

Usage Guidelines4/5

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

The description clearly conveys when to use the tool: when actual repository files need to be inspected, rather than relying only on metadata. It also names the companion tools and cleanup routine, but it does not explicitly state when not to use it or contrast it directly with the kubesearch_* alternatives.

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

Deploy Server