Skip to main content
Glama
xrmghost

MCP Azure DevOps Server

by xrmghost
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

list_files

Browse repository contents by listing files at a specified path within Azure DevOps projects to manage source code and track changes.

Instructions

Lists files in a repository at a specified path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
repository_idYesThe name or ID of the repository.
pathYesThe path to list files from.

Implementation Reference

  • mcp_azure_devops/azure_devops_client.py:674-680 (handler)
    The core handler function that lists files in an Azure DevOps git repository using the GitClient API.
    def list_files(self, project, repository_id, path):
    return self.git_client.get_items(
        project=project,
        repository_id=repository_id,
        scope_path=path,
        recursion_level='full'
    )
  • mcp_azure_devops/server.py:476-497 (schema)
    The input schema definition for the list_files tool, specifying parameters project, repository_id, and path.
        name="list_files",
    description="Lists files in a repository at a specified path.",
    inputSchema={
        "type": "object",
        "properties": {
            "project": {
                "type": "string", 
                "description": "The name or ID of the project."
            },
            "repository_id": {
                "type": "string", 
                "description": "The name or ID of the repository."
            },
            "path": {
                "type": "string", 
                "description": "The path to list files from."
            },
        },
        "required": ["project", "repository_id", "path"],
        "additionalProperties": False
    }
),
  • mcp_azure_devops/server.py:1051-1052 (registration)
    The dispatch logic in the call_tool handler that routes 'list_files' invocations to the client method.
    elif name == "list_files":
    return self.client.list_files(**arguments)

Tool Definition Quality

B3.1/5.0
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 it 'lists files' but doesn't describe what information is returned (e.g., file names, sizes, types), whether there's pagination, rate limits, authentication requirements, or error conditions. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 function without unnecessary words. It's front-loaded with the core purpose and appropriately sized for a straightforward listing tool.

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 read-only listing tool with no output schema, the description is minimally adequate but incomplete. It covers the basic action and parameters but lacks details on return format, error handling, or behavioral constraints that would help an agent use it correctly in context with sibling tools.

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?

Schema description coverage is 100%, so the schema already documents all three parameters (project, repository_id, path) with clear descriptions. The description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints, meeting the baseline for high schema coverage.

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 ('files in a repository at a specified path'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_repositories' or 'list_wiki_pages', which would require mentioning it specifically lists files rather than other repository contents.

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 sibling tools like 'get_file_content' for retrieving file details or 'list_repositories' for listing repositories instead of files, leaving the agent to infer usage context from the tool name alone.

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