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

ado-workflows-mcp

by grimlor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_repo_file_content

Fetch the content of a single file from any branch, commit, or tag in an Azure DevOps repository. Returns path, content, encoding, and size.

Instructions

Fetch a single file's content from any branch, commit, or tag.

Returns a dict with keys: path, content, encoding, size_bytes.

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

Args: path: File path within the repository. ref: Branch name, commit SHA, or tag. None = default branch. 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>",
      "repository": "<repository>",
      "project": "<project>",
      "working_directory": "<working_directory>"
    },
    "name": "get_repo_file_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
refYes
repositoryYes
projectYes
working_directoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description bears full burden. It discloses the return dict keys and context resolution behavior. However, it lacks details on error scenarios, authentication needs, or rate limits, resulting in moderate transparency.

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 concise with a clear summary followed by a bullet-like list of parameters. Every sentence provides essential information without redundancy or fluff.

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

Completeness4/5

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

Given the presence of an output schema (covering return values) and the description's coverage of context resolution and parameter semantics, it is mostly complete. It could mention potential errors (e.g., file not found) but still provides sufficient context for an AI agent.

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?

With 0% schema description coverage, the description adds significant meaning: it explains that 'ref' can be a branch, commit, or tag (null=default), and that 'repository' and 'project' override context. This effectively compensates for the schema's lack of parameter descriptions.

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 explicitly states 'Fetch a single file's content from any branch, commit, or tag,' which is a specific verb and resource. It distinguishes from sibling tools like get_pr_file_contents by not being limited to pull requests.

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?

The description explains context resolution from a cached RepositoryContext unless explicit params are provided, giving clear guidance on when to use parameters. It does not explicitly compare to siblings, but the purpose implicitly differentiates.

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