Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Diff two commits

devops_repository_diffs_commits
Read-only

Compare a repository's base and target commit SHAs to retrieve their differences for code review or change analysis.

Instructions

Get the difference between the base and target commits.

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>",
      "base_commit": "<base_commit>",
      "target_commit": "<target_commit>"
    },
    "name": "devops_repository_diffs_commits"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_commitYesBase commit SHA — full 40-character hex (e.g. lastMergeTargetCommit).
repository_idYesRepository name or ID.
target_commitYesTarget commit SHA — full 40-character hex (e.g. lastMergeSourceCommit).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/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. The description adds nothing beyond that — no statement of what the diff output covers, whether renames/binary files are handled, or any size or rate constraints. It essentially restates the title with the two argument roles.

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?

A single front-loaded sentence with no filler, which is efficient. It borders on under-specification rather than verbosity, but nothing written is wasted.

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?

An output schema exists and the input schema is fully documented, so much of the burden is carried elsewhere. Still, for a diff tool sitting among several diff/change-oriented siblings, the absence of any routing or result-shape context leaves a real gap.

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%, and the schema already explains that base and target commits are full 40-character SHAs with example sources. The description adds no further meaning about parameter interaction (e.g., what direction the diff runs or whether order matters), so the baseline of 3 applies.

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 states a specific verb ("Get the difference") and resource ("between the base and target commits"), which is unambiguous on its own. It does not, however, distinguish this from near siblings like devops_repository_commit_changes or devops_get_item_content_diff, leaving the agent to infer the distinction from names alone.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from the text whether this is the right tool for comparing a commit against its parent versus comparing two arbitrary commits, or how it relates to devops_repository_commit_changes.

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