Skip to main content
Glama
fovi-llc

Radicle + GitHub MCP Server

by fovi-llc

rad_init

Initialize a new Radicle repository by specifying its name, description, and visibility settings to start peer-to-peer code collaboration.

Instructions

Initialize a new Radicle repository.

Args:
    name: Name of the repository
    description: Description of the repository
    public: Whether the repository should be public (default: True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionNo
publicNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the rad_init tool, decorated with @mcp.tool() which registers it with the MCP server. It constructs and executes the 'rad init' command using the shared run_rad_command helper.
    @mcp.tool()
    async def rad_init(name: str, description: str = "", public: bool = True) -> str:
        """
        Initialize a new Radicle repository.
        
        Args:
            name: Name of the repository
            description: Description of the repository
            public: Whether the repository should be public (default: True)
        """
        command = ["rad", "init", "--name", name]
        
        if description:
            command.extend(["--description", description])
        
        if public:
            command.append("--public")
        else:
            command.append("--private")
        
        result = await run_rad_command(command)
        
        if result["success"]:
            return f"✅ Successfully initialized Radicle repository '{name}'\n{result['stdout']}"
        else:
            return f"❌ Failed to initialize repository: {result['stderr']}"
  • Shared helper function used by rad_init (and other tools) to execute radicle CLI commands asynchronously, handling subprocess execution, output capture, and error cases.
    async def run_rad_command(command: List[str], cwd: Optional[str] = None) -> Dict[str, Any]:
        """
        Run a rad command and return the result.
        
        Args:
            command: List of command arguments starting with 'rad'
            cwd: Working directory to run the command in
            
        Returns:
            Dictionary with stdout, stderr, and return_code
        """
        try:
            # Ensure command starts with 'rad'
            if not command or command[0] != "rad":
                command = ["rad"] + command
                
            logger.info(f"Running command: {' '.join(command)}")
            
            process = await asyncio.create_subprocess_exec(
                *command,
                stdout=asyncio.subprocess.PIPE,
                stderr=asyncio.subprocess.PIPE,
                cwd=cwd
            )
            
            stdout, stderr = await process.communicate()
            
            return {
                "stdout": stdout.decode("utf-8").strip(),
                "stderr": stderr.decode("utf-8").strip(),
                "return_code": process.returncode,
                "success": process.returncode == 0
            }
            
        except FileNotFoundError:
            return {
                "stdout": "",
                "stderr": "rad command not found. Please ensure Radicle is installed.",
                "return_code": 127,
                "success": False
            }
        except Exception as e:
            return {
                "stdout": "",
                "stderr": f"Error running command: {str(e)}",
                "return_code": 1,
                "success": False
            }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. It states the action but doesn't mention what 'initialize' entails (e.g., creates local files, sets up tracking, requires authentication), potential side effects, error conditions, or what the output contains. For a creation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured with a clear purpose statement followed by a bullet-point parameter explanation. Every sentence adds value, though the parameter section could be slightly more concise by integrating defaults into the main text rather than a parenthetical note.

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 the tool has an output schema (which handles return values), 3 parameters with good semantic coverage in the description, and no annotations, the description is minimally adequate. However, for a repository creation tool, it should ideally mention authentication requirements, file system impacts, or relationship to other Radicle commands to be fully complete.

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?

The description adds meaningful semantic context for all three parameters beyond the 0% schema coverage. It explains that 'name' is the repository name, 'description' is its description, and 'public' controls visibility with a default value. This compensates well for the lack of schema descriptions, though it doesn't detail constraints like name format or length limits.

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 specific action ('Initialize a new Radicle repository') with the exact resource type, distinguishing it from sibling tools like rad_clone (which clones existing repos) or rad_sync (which syncs changes). The verb 'initialize' precisely indicates creation from scratch rather than other repository operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing to be in a Radicle project directory), when not to use it (e.g., if a repository already exists), or how it differs from similar tools like rad_clone for existing repositories. The only implicit context is that it creates new repositories.

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/fovi-llc/radicle-mcp'

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