Skip to main content
Glama

list_repositories

Retrieve a list of all initialized Python repositories to analyze code structure and dependencies using the Nuanced MCP Server.

Instructions

List all initialized repositories.

Returns: List of initialized repositories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the list_repositories tool. It lists all initialized code graph repositories, indicating the active one with an asterisk.
    @mcp.tool()
    def list_repositories() -> str:
        """List all initialized repositories.
        
        Returns:
            List of initialized repositories
        """
        global _code_graphs, _active_repo
        
        if not _code_graphs:
            return "No repositories have been initialized yet."
        
        repo_list = []
        for repo_path in _code_graphs.keys():
            prefix = "* " if repo_path == _active_repo else "  "
            repo_list.append(f"{prefix}{repo_path}")
        
        return "Initialized repositories:\n" + "\n".join(repo_list) + "\n\n* indicates active repository"
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. It states the tool lists repositories and returns a list, but lacks critical behavioral details: it doesn't specify the format of the returned list (e.g., names, paths, metadata), whether it includes all repositories or only accessible ones, or any permissions required. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 very concise with two short sentences that directly state the action and return value. It's front-loaded with the main purpose. However, the second sentence ('Returns: List of initialized repositories') is somewhat redundant with the first, slightly reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'initialized' means in this context, the structure of the returned list, or any error conditions. For a tool that likely interacts with a repository system, more context on behavior and output is needed to be fully helpful.

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, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics beyond the schema, so it meets the baseline of 4 for tools with no parameters. It correctly omits any parameter discussion, which is appropriate.

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 ('initialized repositories'), making the purpose immediately understandable. It distinguishes from siblings like 'analyze_change_impact' or 'get_function_call_graph' by focusing on listing rather than analysis. However, it doesn't explicitly differentiate from 'switch_repository' which might also involve repository selection.

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., whether repositories must be initialized first), nor does it contrast with siblings like 'switch_repository' for repository selection or 'initialize_graph' for setup. Usage is implied but not explicitly stated.

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

Related 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/mattmorgis/nuanced-mcp'

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