Skip to main content
Glama

list_repos

Lists all configured git repositories to aggregate commit data for automated CV/resume generation with LaTeX formatting support.

Instructions

List all configured git repositories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the list_repos tool handler. It iterates over the REPO_DICT, formats a list of configured repositories with paths, adds total count and usage instructions, and returns as TextContent.
    async def list_repos_tool() -> list[TextContent]:
        """List all configured repositories."""
        if not REPO_DICT:
            return [TextContent(
                type="text",
                text="No repositories configured"
            )]
        
        output = "Configured Repositories:\n\n"
        for name, path in REPO_DICT.items():
            output += f"- {name}: {path}\n"
        
        output += f"\nTotal: {len(REPO_DICT)} repository" + ("ies" if len(REPO_DICT) > 1 else "")
        output += "\n\nUsage:\n"
        output += "- Use 'get_git_log_by_repo' to get commits from a specific repo\n"
        output += "- Use 'get_git_log_all_repos' to get commits from all repos"
        
        return [TextContent(type="text", text=output)]
  • Registration of the list_repos tool in the @app.list_tools() function, specifying the name, description, and empty input schema (no parameters required).
    Tool(
        name="list_repos",
        description="List all configured git repositories",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
  • Input schema for the list_repos tool, defining an object with no properties (no input parameters needed).
    inputSchema={
        "type": "object",
        "properties": {}
    }
  • Dispatch logic in the @app.call_tool() handler that routes calls to the list_repos tool to the list_repos_tool function.
    elif name == "list_repos":
        return await list_repos_tool()
  • Helper function parse_repos() that parses the REPOS environment variable into REPO_DICT, which is used by list_repos_tool to list repositories. Includes fallbacks for REPO_PATH and current directory.
    def parse_repos() -> dict:
        """Parse REPOS environment variable into a dictionary."""
        repos = {}
        
        # Parse REPOS if provided
        if REPOS:
            for repo_entry in REPOS.split(","):
                if ":" in repo_entry:
                    name, path = repo_entry.split(":", 1)
                    repos[name.strip()] = path.strip()
        
        # Backward compatibility: if REPO_PATH is set and no REPOS, use it as default
        if REPO_PATH and not repos:
            repos["default"] = REPO_PATH
        
        # If nothing configured, use current directory as default
        if not repos:
            repos["default"] = os.getcwd()
        
        return repos
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 mentions 'all configured git repositories' which implies a read operation, but doesn't specify whether this requires authentication, what format the output takes, or if there are any rate limits. The description is minimal and lacks important behavioral context.

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 a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple tool and gets straight to the point.

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?

For a simple read operation with no parameters and no output schema, the description is minimally adequate. However, without annotations or output schema, it should ideally provide more context about what 'configured git repositories' means and what format the list takes. The description is complete enough for basic understanding but lacks depth.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description doesn't need to add parameter information, and it correctly doesn't mention any parameters. This meets expectations for a parameterless tool.

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 ('List') and the resource ('all configured git repositories'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_git_log_all_repos', but the verb+resource combination is specific enough for basic understanding.

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 'get_git_log_all_repos' or 'get_git_log_by_repo'. It simply states what the tool does without context about appropriate use cases or prerequisites.

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/eyaab/cv-resume-builder-mcp'

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