Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Get file content

devops_repository_item_content
Read-only

Fetch raw file content from an Azure DevOps repository path at a specific commit, enabling AI assistants to inspect exact source files for reviews or troubleshooting.

Instructions

Get raw file content for a repository path at a specific version.

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": {
      "repository_id": "<repository_id>",
      "path": "<path>",
      "version": "<version>"
    },
    "name": "devops_repository_item_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath of the item, e.g. src/foo.cs
versionYesCommit ID to fetch the file from.
repository_idYesRepository name or ID.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally, and an output schema exists. The description contributes only the words "raw" and "at a specific version," which hint that content is unparsed and version-pinned but say nothing about size limits, encoding, or binary files.

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?

One tightly written sentence with the resource and scope front-loaded and no filler. It is perhaps too terse for the ambiguity it leaves, but nothing is wasted.

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?

With three fully documented required parameters, an output schema, and read-only annotations, the definition covers what an agent needs to invoke the call. Only the sibling disambiguation (content vs. diff) is missing.

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 repository_id, path, and version with examples. The description restates those concepts without adding format, encoding, or edge-case semantics beyond what the schema provides.

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?

States a specific verb and resource ("Get raw file content") plus scope ("for a repository path at a specific version"). It does not distinguish itself from close siblings such as devops_get_item_content_diff, so an agent must infer that this returns a whole file rather than a diff.

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?

No explicit when-to-use, when-not-to-use, or alternative-tool guidance. The requirement of a commit ID is implied only by the phrase "at a specific version," leaving the agent to guess whether a diff or repository-metadata sibling is the better call.

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