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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetStructureVersionDiff

Compares two ABAP structure versions from version history and returns their unified diff, enabling change review and version comparison.

Instructions

[read-only] Compares the two ABAP structure 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": "GetStructureVersionDiff"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_uri_toYesOpaque content_uri of the NEW/compare version, from the ABAP structure's version history.
content_uri_fromYesOpaque content_uri of the OLD/base version, from the ABAP structure'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 GetStructureVersions entry)."New value: +"Opaque content_uri of the OLD/base version, from the ABAP structure's version history."
    • changedInput schema / properties / content_uri_to / description
      Previous value: -"Opaque content_uri of the NEW/compare version (from a GetStructureVersions entry)."New value: +"Opaque content_uri of the NEW/compare version, from the ABAP structure's version history."
  2. Addedv8.5.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose important behavior: read-only operation, unified diff output, and special batch-mode recording semantics where content is empty and retrieved later by number. It does not cover permissions or error conditions, but the key behavioral traits are present.

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?

Front-loads the read-only marker and the core comparison purpose, then adds only the necessary batch-mode caveat. The description is dense but every clause earns its place.

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?

For a read-only diff tool with no output schema, the description gives sufficient context: what is compared, what is returned, and how batch mode changes the response. Nothing critical for correct invocation 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 coverage is 100%, so both parameters are already documented in the schema, including old/base vs new/compare semantics. The description reinforces that they are version-history entries but adds no syntax or format detail 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: it compares two ABAP structure versions and returns their unified source diff. This clearly distinguishes it from sibling version-history tools such as GetStructureVersionSource and GetStructureVersions.

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?

Provides clear context that the inputs are version-history entries and that the tool answers a diff. It does not explicitly name alternatives or exclusions, but the intended use case is unambiguous.

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