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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetFunctionModuleVersions

Lists the version history of an ABAP function module, including version IDs, authors, update times, transport requests, and source URIs for auditing or change tracking.

Instructions

[read-only] Lists the version history of the ABAP function module named by function_module_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": {
      "function_module_name": "<function_module_name>",
      "function_group_name": "<function_group_name>"
    },
    "name": "GetFunctionModuleVersions"
  }
}

Input Schema

NameRequiredDescriptionDefault
function_group_nameYesOwning function group name (required).
function_module_nameYesABAP function module 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?

No annotations are supplied, yet the description declares read-only status and, more importantly, explains the batch ('Recordable') behavior: in batch mode the call is recorded under the next number and returns empty content, with the real answer read later by number. That is meaningful non-obvious context. It stops short of describing error behavior for a nonexistent module or any pagination/limits on the version 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?

The core purpose is front-loaded in the first clause and the return-field list and batch note follow in order of relevance. It is dense but every clause carries information; the field enumeration is slightly long but 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?

With no output schema, the description usefully documents the shape of each version record and the content_uri handle, and it covers the batch recording model. For a simple two-parameter read tool this is nearly complete; only failure/empty-list behavior is unaddressed.

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 both parameters are already documented, and the baseline is 3. The description only echoes function_module_name as the subject and says nothing about function_group_name, adding no semantics 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?

The description names a specific verb and resource ('Lists the version history of the ABAP function module named by function_module_name') and enumerates the returned fields (versionId, author, updatedAt, transportRequest, content_uri), which implicitly separates it from siblings like GetFunctionModuleVersionSource and GetFunctionModuleVersionDiff. It never names those siblings outright, so routing still requires inference.

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 only implied by the resource: an agent can infer it is for inspecting a module's version list. There is no statement of when to prefer it over GetFunctionModuleVersionSource/VersionDiff, and no preconditions or exclusions are 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