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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetFunctionModuleVersionSource

Reads the ABAP source code of a specified function module version via content_uri, so you can inspect historical version content.

Instructions

[read-only] Reads the source of the ABAP function module version named by content_uri, an entry of the ABAP function module's version history. 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": {
      "content_uri": "<content_uri>"
    },
    "name": "GetFunctionModuleVersionSource"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_uriYesOpaque content_uri of a version, from the ABAP function module's version history.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv20.1.0
    • changedInput schema / properties / content_uri / description
      Previous value: -"Opaque content_uri taken from a GetFunctionModuleVersions entry."New value: +"Opaque content_uri of a version, from the ABAP function module's version history."
  2. Addedv8.5.0

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden and does so well: it marks the tool as read-only and explains the important batch-mode recording behavior, including empty content and reading the answer later by number. It does not cover error behavior for stale or invalid URIs, which keeps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the read-only marker and core action. The batch-mode sentence is dense but every clause adds operational meaning for correct invocation.

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 read tool with no output schema, the description covers the essential return expectation (source content, with batch-mode empty content). It could mention failure modes for invalid content_uri, but otherwise it is complete enough to invoke correctly.

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 already has an adequate description. The description reinforces that content_uri names a version-history entry, but adds no new format, syntax, or selection details beyond the schema baseline.

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?

States a specific verb and resource: reads the source of the ABAP function module version identified by content_uri. The version-history qualifier clearly distinguishes it from siblings that list versions or compute version diffs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the usage context clear: call it with a content_uri that came from the function module's version history. It does not explicitly name GetFunctionModuleVersions or GetFunctionModuleVersionDiff as alternatives, so it stops short of full routing 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