ABAP-ADT-API MCP-Server

ddicElement

Retrieve information about ABAP DDIC elements using the ABAP-ADT-API MCP server. Access metadata, associations, extension views, and secondary objects for development and analysis tasks.

Instructions

Retrieves information about a DDIC element.

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": {
      "path": "<path>"
    },
    "name": "ddicElement"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	The path to the DDIC element.
`getTargetForAssociation`	No	Whether to get the target for association.
`getExtensionViews`	No	Whether to get extension views.
`getSecondaryObjects`	No	Whether to get secondary objects.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Mar 20, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a safe read operation ('Retrieves') but does not disclose what is returned, whether authentication is required, error behavior, or how the optional flags affect the response.

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 a single, front-loaded sentence with no wasted words. It communicates the core purpose efficiently and earns its place without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the one-sentence description is insufficient. It doesn't explain what information is returned or how the optional boolean flags modify the result, leaving an agent without enough context for effective invocation.

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%, so the baseline is 3. The description adds no parameter-specific context beyond what the schema already provides; the schema descriptions for path and the three boolean flags are clear and self-contained.

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?

The description uses a specific verb ('Retrieves') and names a specific resource ('a DDIC element'), clearly identifying this as a read/information tool. However, it doesn't specify what kind of information is returned, so it doesn't distinguish itself from sibling tools like objectStructure, findDefinition, or getObjectSource.

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?

The description provides no guidance on when to use this tool versus alternatives like searchObject or findObjectPath. No context about prerequisites (e.g., login/session), exclusions, or references to sibling tools are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server