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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetDdlVersionDiff

Compares two CDS view DDL source versions from version history and returns their unified diff.

Instructions

[read-only] Compares the two CDS view (DDL source) 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": "GetDdlVersionDiff"
  }
}

Input Schema

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

TDQS

A3.8/5.0
Behavior4/5

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

With no structured annotations, the description carries the full burden and does well: it declares '[read-only]', states the answer is a unified diff of the sources, and explains the non-obvious batch-mode behavior (recorded under a number, returns empty content, answer read later by number). It omits any note on diff size/truncation or error behavior for invalid uris.

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?

Two sentences, front-loaded with the read-only marker and the core comparison, then the batch-mode caveat. No filler and every clause conveys operational information.

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?

Return value is described qualitatively ('unified diff of their sources') despite no output schema, and the batch recording contract is spelled out. What is missing is how to acquire the content_uris and whether diff output is paginated or truncated.

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 labels content_uri_from as OLD/base and content_uri_to as NEW/compare. The description restates the same pairing without adding format, provenance, or how to obtain the opaque uris, so baseline 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?

States a specific verb and resource: compares two CDS view (DDL source) versions and returns the unified diff of their sources. The old/new mapping via content_uri_from/content_uri_to is explicit, so an agent can distinguish it from sibling source/version-list tools like GetDdlVersionSource and GetDdlVersions, though it never names those alternatives directly.

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?

Says the two content_uris are 'entries of its version history', which implies a prior GetDdlVersions call but never states that prerequisite outright. There is no explicit when-to-use vs GetDdlVersionSource (single version) guidance, so the routing is only implied.

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