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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetInterfaceVersionSource

Reads the ABAP source code for a specific interface version using its content_uri from version history, enabling inspection of historical interface definitions.

Instructions

[read-only] Reads the source of the ABAP interface version named by content_uri, an entry of the ABAP interface'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": "GetInterfaceVersionSource"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_uriYesOpaque content_uri of a version, from the ABAP interface'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 GetInterfaceVersions entry."New value: +"Opaque content_uri of a version, from the ABAP interface's version history."
  2. 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 real work: it declares read-only behavior and explains the non-obvious batch-mode contract (call is recorded under the next number, returns empty content, answer retrieved later by number). It stops short of covering failures, invalid/expired URIs, or whether the full source is always returned.

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 sentences, front-loaded with the [read-only] marker and the core action, then the batch caveat. Dense but every clause carries information; the batch sentence is long but justified for a non-obvious behavior.

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 single-parameter read with no output schema, the description covers purpose, input provenance, and the one surprising behavioral mode. It leaves the return shape (raw ABAP source text) and size/handling characteristics implicit, which is a modest gap given no output schema exists.

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 sole parameter's schema text already says it is an opaque content_uri from the version history, so the description's phrasing repeats rather than extends it. Baseline 3 is correct; a note on obtaining or scoping the URI would have raised it.

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?

Names a specific verb and resource (reads the source of an ABAP interface version) and pins the input to a version-history entry, which separates it from the listing/diff siblings by implication. It never names GetInterfaceVersions or GetInterfaceVersionDiff explicitly, so the differentiation is inferred rather than stated.

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?

Saying content_uri is 'an entry of the ABAP interface's version history' hints that a version-listing call must come first, but the description never states that prerequisite or points at GetInterfaceVersions as the source of the URI. No when-not-to-use guidance versus GetInterface or the diff tool.

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