Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Get file diff

devops_get_item_content_diff
Read-only

Compare two file versions and return only changed hunks with numbered lines, marking additions and removals for code review.

Instructions

Get textual diff between two versions of a file (changed hunks only). Lines are numbered; added lines are prefixed with '+', and removed with '-'. For full content of specific file, use item content tool with target 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>",
      "base_version": "<base_version>",
      "target_version": "<target_version>"
    },
    "name": "devops_get_item_content_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath of the file to diff, e.g. src/foo.cs
base_versionYesBase commit ID, e.g. lastMergeTargetCommit.
repository_idYesRepository name or ID.
target_versionYesTarget commit ID, e.g. lastMergeSourceCommit.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely non-redundant output semantics: hunk-only scope, line numbering, and '+'/'-' prefixes. It does not mention size limits, truncation, or behavior on identical versions, which are the remaining unknowns for a diff call.

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?

Two sentences, front-loaded with the operation and its scope, then the alternative. No filler; the output-format detail is compressed into a single clause.

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 a 100%-covered schema, an output schema, and safety annotations, the description only needs to add scope and routing, which it does. Minor gaps around large-diff truncation and identical-version behavior keep it from a 5.

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 all four parameters (path, base_version, target_version, repository_id) are already documented with examples. The description adds only the framing of "two versions of a file" and does not clarify version resolution rules or precedence 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?

States a specific verb and resource ("Get textual diff between two versions of a file") and immediately scopes it ("changed hunks only"), which distinguishes it from the full-content sibling it names. An agent can tell exactly what this returns without opening the schema.

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?

Explicitly routes the agent to the alternative ("For full content of specific file, use item content tool with target version"), giving a clear when-to-use-this vs when-to-use-that split. No exclusions for edge cases (e.g., binary files, very large diffs) are mentioned, so it stops short of a 5.

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