Skip to main content
Glama
Sign In
mcp-abap-adt

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetClassVersionDiff

Compares two ABAP class versions from version history and returns the unified diff of their source code, showing exactly what changed between the old and new versions.

Instructions

[read-only] Compares the two ABAP class versions named by content_uri_from and content_uri_to, entries of its version history: answers the unified diff of their sources. Recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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": {
      "content_uri_from": "<content_uri_from>",
      "content_uri_to": "<content_uri_to>"
    },
    "name": "GetClassVersionDiff"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_uri_toYesOpaque content_uri of the NEW/compare version, from the ABAP class's version history.
content_uri_fromYesOpaque content_uri of the OLD/base version, from the ABAP class's version history.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv20.1.0
    • changedInput schema / properties / content_uri_from / description
      Previous value: -"Opaque content_uri of the OLD/base version (from a GetClassVersions entry)."New value: +"Opaque content_uri of the OLD/base version, from the ABAP class's version history."
    • changedInput schema / properties / content_uri_to / description
      Previous value: -"Opaque content_uri of the NEW/compare version (from a GetClassVersions entry)."New value: +"Opaque content_uri of the NEW/compare version, from the ABAP class's version history."
  2. Addedv8.5.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does well: it marks the tool as read-only, specifies the return as a unified diff, and importantly discloses batch-mode behavior where the call returns empty content and the answer is read by number later. It does not cover error behavior or permissions, so it is strong but not exhaustive.

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?

The description is front-loaded with the read-only marker and the core diff purpose, then adds the batch-mode caveat. It is reasonably compact and every sentence contributes useful information, though the batch sentence is dense.

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?

For a two-parameter read-only diff tool with no output schema, the description gives enough to call it correctly: it explains the inputs are class version-history URIs, the output is a unified diff, and batch mode returns empty content. Error handling and prerequisite permissions are omitted but not critical for correct invocation.

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 both content_uri_from and content_uri_to are already documented as opaque version-history URIs for the old/base and new/compare versions. The description restates these parameters but adds little semantic detail beyond the schema, so the baseline 3 is appropriate.

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 states a specific verb and resource: compares two ABAP class versions and returns the unified diff of their sources. This clearly distinguishes it from sibling tools such as GetClassVersionSource, which retrieves source rather than diffing versions.

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

Usage Guidelines3/5

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

Usage is implied by the purpose: use it when a unified diff between two class versions is needed. However, the description does not explicitly say when to prefer this over GetClassVersionSource, GetObjectVersionDiff, or other version-diff siblings, and it gives no exclusions or prerequisites.

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