Skip to main content
Glama

list_repositories

Retrieve all repositories in an Azure DevOps project to manage codebase access and organization.

Instructions

Lists all repositories in a project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.

Implementation Reference

  • The core handler function that executes the list_repositories tool logic by calling the Azure DevOps Git client to retrieve repositories for a given project.
    def list_repositories(self, project):
        return self.git_client.get_repositories(project=project)
  • The input schema definition for the list_repositories tool, specifying that a 'project' parameter is required.
    types.Tool(
        name="list_repositories",
        description="Lists all repositories in a project.",
        inputSchema={
            "type": "object",
            "properties": {
                "project": {
                    "type": "string", 
                    "description": "The name or ID of the project."
                },
            },
            "required": ["project"],
            "additionalProperties": False
        }
    ),
  • The registration and dispatch logic in the MCP server's tool execution handler that routes calls to list_repositories to the client implementation.
    elif name == "list_repositories":
        return self.client.list_repositories(**arguments)
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 tool lists repositories but fails to describe key behaviors such as pagination, sorting, filtering, error handling, or authentication requirements, which are critical for a list operation.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for its simple function, earning full marks for conciseness.

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 does not address behavioral aspects like return format, pagination, or error cases, which are essential for a list tool in a context with many sibling tools and no structured output guidance.

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 input schema has 100% description coverage, with the 'project' parameter clearly documented. The description adds no additional meaning beyond the schema, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 ('Lists') and resource ('all repositories in a project'), providing a specific verb+resource combination. However, it does not distinguish this tool from potential siblings like 'list_files' or 'list_wiki_pages', which reduces it from a perfect 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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or comparison to sibling tools such as 'get_projects' or 'list_files', leaving the agent without usage direction.

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/xrmghost/mcp-azure-devops'

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