Skip to main content
Glama
fovi-llc

Radicle + GitHub MCP Server

by fovi-llc

rad_remote_list

List remote repositories connected to a Radicle project to manage collaboration links and track peer connections.

Instructions

List remotes in a Radicle repository.

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 handler function for rad_remote_list tool. It executes the 'rad remote' command using the run_rad_command helper and formats the output. Registered via @mcp.tool() decorator.
    @mcp.tool()
    async def rad_remote_list(repository_path: str = ".") -> str:
        """
        List remotes in a Radicle repository.
        
        Args:
            repository_path: Path to the repository (default: current directory)
        """
        result = await run_rad_command(["rad", "remote"], cwd=repository_path)
        
        if result["success"]:
            if result["stdout"]:
                return f"🌐 Remotes in repository:\n{result['stdout']}"
            else:
                return "🌐 No remotes found in repository"
        else:
            return f"❌ Failed to list remotes: {result['stderr']}"
  • Shared helper function used by multiple radicle tools, including rad_remote_list, to execute 'rad' CLI commands asynchronously.
    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 the full burden of behavioral disclosure. It states it 'List remotes' but doesn't describe what a 'remote' is in Radicle context, how results are formatted, if it's read-only, or any error conditions. This leaves significant gaps for agent understanding.

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 appropriately sized with two sentences: one stating the purpose and another explaining the single parameter. It's front-loaded with the main function and wastes no words, making it efficient and easy to parse.

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 one parameter and an output schema exists, the description covers the basics but lacks context about Radicle-specific behavior and relationships with sibling tools. It's minimally viable but leaves the agent needing to infer details from the output schema or external knowledge.

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 description adds the parameter 'repository_path' with a brief explanation and default value, which provides some meaning beyond the input schema (which has 0% description coverage). However, it doesn't explain path format requirements or validation rules, so it only partially compensates for the schema gap.

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 verb 'List' and resource 'remotes in a Radicle repository', making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'rad_status' or 'rad_sync' which might also involve repository operations, so it doesn't reach the highest score.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention sibling tools like 'rad_status' (which might show remote status) or 'rad_sync' (which might sync remotes), leaving the agent without context for tool selection.

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