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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetFunctionModuleVersionDiff

Compares two ABAP function module versions from version history and returns a unified diff of their source code.

Instructions

[read-only] Compares the two ABAP function module 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": "GetFunctionModuleVersionDiff"
  }
}

Input Schema

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

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it declares [read-only] and explains the batch-mode recording contract (call recorded under the next number, returns empty content, answer retrieved later by number). It does not cover authorization requirements or behavior on invalid/stale content URIs.

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?

Front-loaded with the read-only marker and the core purpose, then a second sentence for the batch contract. The batch sentence is dense but every clause (recording, empty answer, read by number) carries operational meaning; no filler.

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?

No output schema exists, and the description compensates by stating the return is a unified diff of the sources, plus the batch-mode return caveat. For a two-required-param read tool this is close to complete; only error/precondition behavior is absent.

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 already labels content_uri_to as the NEW/compare version and content_uri_from as the OLD/base version. The description restates the same old-vs-new mapping and adds that the URIs come from the version history, but contributes no format or sourcing detail beyond the schema.

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 - compares two ABAP function module versions identified by content_uri_from/content_uri_to - and names the return value (unified source diff). It does not explicitly contrast itself with the nearby GetFunctionModuleVersionSource or GetFunctionModuleVersions, so sibling differentiation relies on the tool name.

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 wording: you compare two entries of a function module's version history. There is no explicit guidance on when to prefer this over GetFunctionModuleVersionSource (single version) or the generic GetObjectVersionDiff, and no stated preconditions such as needing both URIs from the version history listing.

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