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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetMetadataExtensionVersionDiff

Compares two CDS metadata extension versions from version history and returns a unified diff of their sources to show what changed between old and new versions.

Instructions

[read-only] Compares the two CDS metadata extension 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": "GetMetadataExtensionVersionDiff"
  }
}

Input Schema

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

TDQS

A4.1/5.0
Behavior5/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 so well: it declares "[read-only]" up front and discloses a genuinely non-obvious trait — that in batch mode the call is only recorded, returns empty content, and its answer must be read back by number. That is exactly the kind of behavior an agent cannot infer from schema or annotations.

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 sentences, front-loaded with the operation and its result before the batch caveat; the marker "[read-only]" leads. The batch sentence is dense but each clause carries information the agent needs, with only slight jargon overhead.

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?

Covers the operation, both inputs' roles, the return value (unified source diff — important since there is no output schema), and the batch read-back protocol. Minor gaps remain on failure modes (invalid/stale content_uri) and whether ordering of from/to is enforced.

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% and the schema already documents both parameters as opaque content_uris with old/base vs new/compare semantics. The description only restates that they are version-history entries, adding no format or acquisition detail beyond the schema, so the baseline 3 applies.

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 ("Compares the two CDS metadata extension versions") and the exact output ("unified diff of their sources"), which cleanly separates it from sibling GetMetadataExtensionVersions (list) and GetMetadataExtensionVersionSource (single source). An agent can pick it out without opening the schema.

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 "entries of its version history" and the old/new pairing, so an agent can infer it must first obtain content_uris from the versions tool. However, no sibling is named, no prerequisite is stated explicitly, and no exclusion (e.g. use GetObjectVersionDiff for other object types) is given.

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