Skip to main content
Glama
fovi-llc

Radicle + GitHub MCP Server

by fovi-llc

rad_sync

Sync a Radicle repository with the peer-to-peer network to update and share code changes across the distributed collaboration platform.

Instructions

Sync a Radicle repository with the network.

Args:
    repository_path: Path to the repository (default: current directory)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repository_pathNo.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function for the 'rad_sync' MCP tool. It is registered via the @mcp.tool() decorator and executes the 'rad sync' command in the given repository path using the run_rad_command helper, returning formatted success or error messages.
    @mcp.tool()
    async def rad_sync(repository_path: str = ".") -> str:
        """
        Sync a Radicle repository with the network.
        
        Args:
            repository_path: Path to the repository (default: current directory)
        """
        result = await run_rad_command(["rad", "sync"], cwd=repository_path)
        
        if result["success"]:
            return f"✅ Successfully synced repository\n{result['stdout']}"
        else:
            return f"❌ Failed to sync repository: {result['stderr']}"
  • Helper function used by rad_sync (and other tools) to execute 'rad' CLI commands asynchronously, capturing stdout/stderr and return code.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Sync') but doesn't explain what this entails—e.g., whether it fetches updates, pushes local changes, handles conflicts, requires network connectivity, or has side effects. 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 brief and front-loaded with the main purpose, followed by parameter details in a structured 'Args' section. There's minimal waste, but it could be slightly more informative without sacrificing conciseness.

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 one parameter with 0% schema coverage and an output schema (which reduces the need to describe return values), the description is minimally adequate. It covers the basic purpose and parameter but lacks details on behavior, usage context, and error handling, making it incomplete for a network sync operation.

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 description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'repository_path' is the 'Path to the repository' with a default of 'current directory', which clarifies beyond the schema's basic type and title. However, it doesn't detail format constraints or examples, leaving some ambiguity.

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?

The description clearly states the action ('Sync') and resource ('a Radicle repository with the network'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'rad_push' or 'rad_status', which might also involve network operations, so it doesn't achieve full sibling differentiation.

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 like 'rad_push' or 'rad_status'. It lacks context about prerequisites, such as whether the repository must be initialized or have remotes set up, and doesn't mention any exclusions or specific scenarios for its use.

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