Skip to main content
Glama
Sign In
ado-workflows-mcp

ado-workflows-mcp

by grimlor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_repo_items

List files and folders at a path on any branch, commit, or tag. Choose recursion level to get flat or full directory contents.

Instructions

List files and folders at a path on any branch, commit, or tag.

Returns a list of dicts, each with keys: path, is_folder, git_object_type, object_id, commit_id, url.

Context (repository, project, org) is resolved from the cached RepositoryContext unless explicit params are provided.

Args: path: Directory path to list. Defaults to "/". ref: Branch name, commit SHA, or tag. None = default branch. recursion: "none", "oneLevel" (default), or "full". repository: Repository name (overrides context). project: Project name (overrides context). working_directory: Optional path for context resolution.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "ref": "<ref>",
      "recursion": "<recursion>",
      "repository": "<repository>",
      "project": "<project>",
      "working_directory": "<working_directory>"
    },
    "name": "list_repo_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
refYes
recursionYes
repositoryYes
projectYes
working_directoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.0

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description details the behavior: what the tool returns, default values for path and recursion, and context resolution. Without annotations, this covers most behavioral aspects, though it does not mention edge cases like empty directories or performance considerations.

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 well-structured with a concise summary, return format note, context explanation, and a bulleted Args list. Every sentence adds value and is front-loaded.

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

Completeness5/5

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

Given the 6 required parameters and presence of an output schema, the description covers all necessary aspects: parameter defaults, override behavior, return format, and recursion options. It is complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining each parameter: path defaults to '/', ref defaults to default branch, recursion options, and how repository/project/working_directory override context. This adds significant meaning beyond the schema.

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 that the tool lists files and folders at a path on any branch, commit, or tag. It specifies the return format as a list of dicts with specific keys, and distinguishes itself from sibling tools like get_repo_file_content (which retrieves single file content) and list_commits (which lists commits).

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

Usage Guidelines4/5

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

It explains context resolution and how to override with explicit parameters, providing clear usage guidance. However, it does not explicitly state when not to use this tool or compare to specific siblings, leaving room for slight improvement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools