mcp-abap-adt

GetTableVersions

Retrieve the version history of a named ABAP table, including version IDs, authors, update timestamps, transport requests, and source content URIs for auditing or rollback planning.

Instructions

[read-only] Lists the version history of the ABAP table named by table_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": {
      "table_name": "<table_name>"
    },
    "name": "GetTableVersions"
  }
}

Input Schema

Name	Required	Description	Default
`table_name`	Yes	ABAP table name.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv8.5.0Jul 1, 2026

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 declares read-only status, discloses the full per-version payload including transport metadata, and explains the non-obvious batch behavior (records a call, returns empty content, answer read later by number). It omits permissions/authorization requirements and whether a missing table errors or returns an empty list.

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 front-loaded sentences with no filler; the read-only tag and the core purpose come first, and the batch caveat comes last. The first sentence is long and field-list-heavy, but every listed field earns its place given no output schema exists.

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, so the description must describe return values — and it does so thoroughly, including content_uri semantics and batch-mode answers. Remaining gaps are edge behavior (nonexistent table, ordering of versions) for an otherwise simple one-parameter read tool.

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 single parameter has a documented description ("ABAP table name"), so the baseline applies. The description restates that table_name identifies the ABAP table but adds no format, case-sensitivity, or lookup-scope 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 ("Lists the version history of the ABAP table named by table_name") and even enumerates the fields each version carries. It does not name its obvious siblings GetTableVersionSource / GetTableVersionDiff, though the mention of the "opaque content_uri" implicitly hints that content retrieval is a separate call.

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+resource rather than stated: there is no explicit "use this when..." or exclusion of GetTableVersionSource/GetTableVersionDiff. The batch-mode paragraph does give procedural guidance for how to invoke it in that context, which lifts it above a bare purpose statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server