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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetMetadataExtensionVersions

List the version history of a CDS metadata extension, including version IDs, authors, timestamps, transport requests, and source content URIs for auditing or rollback.

Instructions

[read-only] Lists the version history of the CDS metadata extension named by metadata_extension_name: each version with its versionId, author, updatedAt, title, the transportRequest (and transportDescription) that produced it when available, and the opaque content_uri that names the version's source. 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": {
      "metadata_extension_name": "<metadata_extension_name>"
    },
    "name": "GetMetadataExtensionVersions"
  }
}

Input Schema

NameRequiredDescriptionDefault
metadata_extension_nameYesCDS metadata extension name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, the description carries the full burden and does well: it self-declares '[read-only]', describes the return fields (versionId, author, updatedAt, title, transportRequest/transportDescription, content_uri), and explains the batch 'recordable' behavior and empty answer. Missing details on pagination/ordering or required authorizations keep it from a 5.

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-loads the read-only marker and the core purpose in the first clause, then details return fields and batch behavior. Dense but no filler; the parentheticals are slightly heavy but each carries 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?

For a single-parameter, no-output-schema tool, the description is nearly complete: it explains return contents and batch semantics. A brief note routing to the diff/source siblings would close the remaining gap.

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 single parameter is fully documented in the schema; the description only restates that the name identifies the extension. Baseline 3 is appropriate since the schema does the heavy lifting and the description adds no format/syntax nuance.

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 precise verb and resource: "Lists the version history of the CDS metadata extension named by metadata_extension_name," and enumerates the fields each version carries. Purpose is unmistakable, though it never names the closely related siblings (GetMetadataExtensionVersionSource, GetMetadataExtensionVersionDiff) to differentiate its scope.

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 verb 'lists the version history,' but there is no explicit when-to-use, when-not, or pointer to the sibling tools that fetch a specific version's source or a diff. The batch-mode note explains operational behavior rather than selection guidance.

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