mcp-abap-adt

GetObjectVersionDiff

Compares two versions from an ABAP object's version history and returns a unified source diff, helping you review changes between a base version and a compare version.

Instructions

[read-only] Compares the two object versions named by content_uri_from and content_uri_to, entries of an object's version history, for the object type named by object_type: returns the unified diff (jsdiff) 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": {
      "object_type": "<object_type>",
      "content_uri_from": "<content_uri_from>",
      "content_uri_to": "<content_uri_to>"
    },
    "name": "GetObjectVersionDiff"
  }
}

Input Schema

Name	Required	Description
`object_type`	Yes	Object type (the same value the version history was read with).
`content_uri_to`	Yes	Opaque content_uri of the NEW/compare version (from the object's version history).
`content_uri_from`	Yes	Opaque content_uri of the OLD/base version (from the object's version history).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv20.1.0Oct 24, 2026

changedInput schema / properties / content_uri_from / description

Previous value: -"Opaque content_uri of the OLD/base version (from a GetObjectVersions entry)."New value: +"Opaque content_uri of the OLD/base version (from the object's version history)."

changedInput schema / properties / content_uri_to / description

Previous value: -"Opaque content_uri of the NEW/compare version (from a GetObjectVersions entry)."New value: +"Opaque content_uri of the NEW/compare version (from the object's version history)."

changedInput schema / properties / object_type / description

Previous value: -"Object type (same value used in GetObjectVersions)."New value: +"Object type (the same value the version history was read with)."

Changed1 schema field changedv8.12.1Jul 23, 2026

changedInput schema / properties / object_type / enum

Previous value: -[
-  "class",
-  "program",
-  "interface",
-  "function_group",
-  "function_module",
-  "table",
-  "structure",
-  "ddl",
-  "domain",
-  "data_element",
-  "package",
-  "behavior_definition",
-  "metadata_extension"
-]New value: +[
+  "class",
+  "program",
+  "interface",
+  "function_module",
+  "table",
+  "structure",
+  "ddl",
+  "behavior_definition",
+  "metadata_extension"
+]

Addedv8.5.0Jul 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it self-declares read-only, discloses the return format (unified jsdiff of sources), and explains the non-obvious batch recording semantics where a call returns empty content and must be read back by number. It omits error/edge behavior (e.g., mismatched object_type, invalid content_uri).

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?

Two dense sentences, front-loaded with the core comparison behavior, with batch semantics in a clearly marked second clause. Efficient, though the batch-mode sentence is jargon-heavy for a first-time reader.

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

Completeness5/5

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

No output schema exists, and the description compensates by naming the return value (unified diff via jsdiff) and the batch-mode answer retrieval. Combined with the prerequisites for the three required parameters, an agent has enough to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3; the description adds real meaning by clarifying that the two content_uris are entries of an object's version history (old/base vs new/compare) and that object_type must match the value history was read with. That goes slightly beyond the schema's own wording.

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 — it compares two object versions named by content_uri_from/content_uri_to for a given object_type and returns the unified jsdiff of their sources. This is far more specific than the sibling GetObjectVersionSource, though it doesn't explicitly say how it relates to the type-specific diffs (GetClassVersionDiff, GetTableVersionDiff, etc.).

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?

It implies the prerequisites (both content_uris must come from the object's version history, and object_type must match how history was read), which is useful context. But it never says when to choose this generic diff over the many type-specific *VersionDiff siblings, leaving the core selection decision to inference.

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

Deploy Server