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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetInterfaceVersions

Lists the version history of an ABAP interface, including version IDs, authors, update dates, titles, transport requests, and source content URIs for tracking changes.

Instructions

[read-only] Lists the version history of the ABAP interface named by interface_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": {
      "interface_name": "<interface_name>"
    },
    "name": "GetInterfaceVersions"
  }
}

Input Schema

NameRequiredDescriptionDefault
interface_nameYesABAP interface name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv8.5.0

TDQS

A3.9/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 labels the operation read-only, describes the returned fields, notes that transportRequest is included "when available," and explains the non-obvious batch-mode recording behavior where calls answer with empty content and are read back by number.

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?

The description is front-loaded with the core purpose, then adds useful return-field and batch-mode context. It is dense but every part contributes; the only minor issue is the long field enumeration.

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 one-parameter, no-output-schema tool, the description is nearly complete: it explains return contents, the transport-request availability caveat, and batch behavior. It stops short of describing ordering or pagination limits, which would be useful for a history listing.

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%, so the schema already documents interface_name. The description only restates that the interface is named by interface_name and does not add format or case-sensitivity details, so the baseline 3 is appropriate.

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?

The description gives a specific verb ("Lists") and resource ("version history of the ABAP interface named by interface_name"), and it enumerates the returned fields, making clear this is a version-listing tool rather than a source or diff tool.

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 stated purpose, but the description does not explicitly say when to choose this over sibling tools such as GetInterfaceVersionSource or GetInterfaceVersionDiff, nor does it state prerequisites or exclusions.

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