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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetStructureVersionSource

Reads the source of a specific ABAP structure version from version history via content_uri, so you can inspect historical structure definitions.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
content_uriYesOpaque content_uri of a version, from the ABAP structure'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 GetStructureVersions entry."New value: +"Opaque content_uri of a version, from the ABAP structure'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 disclosure burden and does well: it labels the operation read-only and explains the unusual batch behavior, including empty content during batch and later answer retrieval by number. It omits error behavior or format details, but covers the key operational traits.

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 tightly written sentences with no wasted text. It front-loads the core read operation before explaining the batch-mode recording 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 one-parameter read tool with no output schema and no annotations, it explains the operation, read-only nature, and batch behavior. Missing details such as error handling or output shape are minor and largely outside the main contract.

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 is already documented as an opaque content_uri from version history. The description restates that meaning but adds no syntax, format, or source-detail beyond the schema.

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 uses a specific verb and resource: 'Reads the source of the ABAP structure version named by content_uri.' It also distinguishes the tool from sibling version tools by tying content_uri to an entry in the structure's version history.

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 clearly indicates the tool is for reading source for a known version URI from the structure version history. It does not explicitly name alternatives such as GetStructureVersions or GetStructureVersionDiff, but the context is sufficient to select it correctly.

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