AgentDrive MCP Server

drive_sandbox_clone

Clone a Git repository into a per-workspace sandbox for isolated execution. The sandbox persists across sessions within the workspace.

Instructions

[EXPERIMENTAL] Clone a git repo into a per-workspace Linux sandbox. Requires Cloudflare Containers on the AgentDrive worker; gracefully degrades to a 503 with "sandbox not configured" otherwise.

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": {
      "workspace_id": "<workspace_id>",
      "url": "<url>"
    },
    "name": "drive_sandbox_clone"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Git repository URL to clone
`depth`	No	Shallow clone depth (default: full clone)
`branch`	No	Branch to check out (default: repo default)
`workspace_id`	Yes	Workspace to clone into. The sandbox persists across MCP sessions per workspace.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the experimental nature, infrastructure dependency, and error handling (graceful 503). It also notes sandbox persistence per workspace. However, it does not describe side effects, idempotency, or success response, which would further aid transparency.

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 two sentences, front-loaded with the purpose and key notes. It uses a clear [EXPERIMENTAL] tag and no unnecessary words. Every sentence adds value.

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?

Given no output schema, the description should explain what the tool returns. It does not. It also omits details like asynchronous behavior or cloning time. However, it covers prerequisites and error cases. The tool is complex, so more completeness would help.

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?

The input schema already describes all 4 parameters with 100% coverage. The description adds some context (e.g., workspace_id implies persistence, depth for shallow clones) but does not significantly enhance meaning beyond the schema. Baseline 3 is appropriate since schema coverage is high.

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 clearly states the tool clones a git repo into a per-workspace Linux sandbox. It specifies the verb 'clone' and distinguishes from sibling tools like drive_sandbox_exec, drive_sandbox_read, and drive_sandbox_commit, which perform different sandbox operations.

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 provides explicit context on requirements (Cloudflare Containers on AgentDrive worker) and graceful degradation behavior (503 on missing config). It does not explicitly state when to use versus alternatives, but the sibling tools suggest different operations, so the usage context is clear enough.

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