Skip to main content
Glama
fovi-llc

Radicle + GitHub MCP Server

by fovi-llc

rad_status

Check the current status of a Radicle repository to monitor its peer-to-peer collaboration state and synchronization details.

Instructions

Get the status of 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 rad_status tool handler function, including registration via @mcp.tool() decorator, input schema via type hints and docstring, and implementation logic that executes the 'rad inspect' command.
    @mcp.tool()
    async def rad_status(repository_path: str = ".") -> str:
        """
        Get the status of a Radicle repository.
        
        Args:
            repository_path: Path to the repository (default: current directory)
        """
        result = await run_rad_command(["rad", "inspect"], cwd=repository_path)
        
        if result["success"]:
            return f"📊 Repository status:\n{result['stdout']}"
        else:
            return f"❌ Failed to get repository status: {result['stderr']}"
  • Supporting utility function run_rad_command used by rad_status to execute shell commands for Radicle CLI.
    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 for behavioral disclosure. It states the tool retrieves status information (implying read-only), but doesn't mention authentication requirements, rate limits, error conditions, or what specific status information is returned. The description provides basic intent but lacks operational details needed for safe invocation.

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 perfectly front-loaded with the core purpose in the first sentence, followed by parameter documentation in a clear 'Args:' section. Every sentence earns its place with no redundant information, 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.

Completeness4/5

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

Given the tool's simple nature (single optional parameter, read-only operation) and the presence of an output schema (which handles return values), the description provides adequate context. It covers the essential what and how, though additional behavioral context would be beneficial since no annotations exist to supplement understanding.

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 context for the single parameter by explaining its purpose ('Path to the repository') and providing the default value ('current directory'), which compensates for the 0% schema description coverage. While it doesn't detail path format requirements or validation rules, it gives sufficient semantic understanding for basic usage.

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 ('Get the status') and target resource ('Radicle repository'), distinguishing it from sibling tools like rad_clone, rad_push, or rad_sync. It uses precise language that immediately conveys the tool's function without ambiguity.

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

Usage Guidelines3/5

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

The description implies usage by mentioning the default parameter value (current directory), suggesting it's for checking repository status locally. However, it lacks explicit guidance on when to use this versus alternatives like rad_sync or rad_remote_list for related repository operations, leaving the agent to infer context from sibling tool names.

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