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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetClassVersions

Lists the version history of a specified ABAP class, including version IDs, authors, timestamps, transport requests, and source content URIs for auditing and rollback.

Instructions

[read-only] Lists the version history of the ABAP class named by class_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": {
      "class_name": "<class_name>"
    },
    "name": "GetClassVersions"
  }
}

Input Schema

NameRequiredDescriptionDefault
class_nameYesABAP class 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 a solid job: it declares '[read-only]', describes the exact response shape including conditional transportRequest/transportDescription ('when available'), and explains the batch recording contract (call recorded by number, empty content returned, answer read after the batch). It stops short of stating pagination, ordering, or what happens for a class with no history.

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 before the field enumeration and the batch caveat; every clause carries information. The single long sentence is dense, and the batch-mode clause is somewhat tacked on, keeping it below 5.

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?

With no output schema, the description compensates by enumerating the returned fields, and it covers the unusual batch-mode semantics. Missing is any pointer to the companion tools that consume versionId/content_uri, which would complete the workflow picture.

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?

Only one parameter, and schema description coverage is 100% ('ABAP class name'). The description adds no syntax guidance (namespace/prefix handling) beyond what the schema already provides, 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 ('Lists the version history of the ABAP class named by class_name') and enumerates the returned per-version fields, so the agent knows exactly what it gets. It only implicitly differentiates from siblings like GetClassVersionSource and GetClassVersionDiff via the 'opaque content_uri' mention, rather than naming them.

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?

The description implies usage (fetch version list, then use content_uri to reach the source) but never states when to pick this over GetClassVersionDiff, GetClassVersionSource, or the generic GetObjectVersions. The batch-mode note gives a conditional usage rule, but only for the recordable path, not for tool selection.

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