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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetTableVersionSource

Reads the ABAP source for a table version identified by its content_uri, helping you inspect historical table definitions from the version history.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
content_uriYesOpaque content_uri of a version, from the ABAP table'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 GetTableVersions entry."New value: +"Opaque content_uri of a version, from the ABAP table'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 provided, the description carries the full burden and does disclose key behavior: it is read-only and, in batch mode, returns empty content while recording the call for later retrieval by number. It does not cover permissions or error behavior, but the most non-obvious behavioral trait is explained.

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?

The description is two sentences with the read-only status and core operation front-loaded, followed by the important batch-mode caveat. Every sentence adds useful information without repetition.

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 is largely complete: it explains what is read, what content_uri identifies, and the unusual batch return behavior. A small gap remains around how to obtain the content_uri or what source format is returned, but the essential calling context is present.

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 schema already describes content_uri as an opaque version identifier from the ABAP table's version history. The description adds little beyond that, so the baseline 3 applies.

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 states a specific verb and resource: reads the source of the ABAP table version named by content_uri. It clearly distinguishes this from version-listing or version-diff siblings by naming the exact object and operation.

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?

It explains that content_uri is an entry from the ABAP table's version history and describes batch-mode recording behavior. It does not explicitly name GetTableVersions or GetTableVersionDiff as alternatives, but the context is clear enough for correct use.

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