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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetDataElement

Reads an ABAP data element by name and returns its ADT metadata—definition, package, and description—for active or inactive versions, enabling inspection of deployed or modified definitions.

Instructions

[read-only] Reads the ABAP data element named by data_element_name in one request: its ADT metadata document (definition, package, description). Returns it under metadata, with part: "metadata". 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": {
      "data_element_name": "<data_element_name>"
    },
    "name": "GetDataElement"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoVersion to read: "active" (default) for deployed version, "inactive" for modified but not activated version.active
data_element_nameYesData element name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv16.0.0
    • changedInput schema / properties / data_element_name / description
      Previous value: -"Data element name (e.g., Z_MY_DATA_ELEMENT)."New value: +"Data element name."
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it declares [read-only], explains the exact return shape (`metadata` key with `part: "metadata"`), and discloses the non-obvious batch/recordable behavior where the call returns empty content and is read back by number. It omits failure behavior (e.g. what happens if the data element does not exist) and permission requirements.

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?

Front-loaded with the [read-only] marker, then purpose, then return shape, then the batch caveat. The final batch sentence is dense but every clause (recorded number, empty content, read back by number) carries information an agent cannot get elsewhere.

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 and no annotations, the description supplies both the safety profile (read-only) and the return structure (`metadata` / `part: "metadata"`), plus batch semantics. Error/absence handling is the main missing piece for a single-object read.

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% and both parameters (data_element_name, version with enum/default) are documented in the schema. The description only restates that the name identifies the object and does not add nuance such as how `version` interacts with the returned metadata, so baseline 3 applies.

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?

Specific verb and resource: 'Reads the ABAP data element named by data_element_name', plus the concrete return payload (ADT metadata document with definition, package, description). It is clearly separable from CreateDataElement/UpdateDataElement/CheckDataElement by verb, though it never names a sibling to contrast with.

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

Usage Guidelines2/5

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

No statement of when to use this instead of CheckDataElement, GetDataElement versions/GetObjectVersionSource, or GetTypeInfo. The batch-mode note is about how a call behaves, not when to choose this tool over alternatives.

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