ABAP-ADT-API MCP-Server

nodeContents

Retrieve contents of ABAP repository tree nodes to access development objects and their structure within ABAP systems.

Instructions

Retrieves the contents of a node in the ABAP repository tree.

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": {
      "parent_type": "<parent_type>"
    },
    "name": "nodeContents"
  }
}

Input Schema

Name	Required	Description
`parent_type`	Yes	The type of the parent node.
`parent_name`	No	The name of the parent node.
`user_name`	No	The user name.
`parent_tech_name`	No	The technical name of the parent node.
`rebuild_tree`	No	Whether to rebuild the tree.
`parentnodes`	No	An array of parent node IDs.

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 provided, the description carries the full burden. It only says 'retrieves', implying read-only, but doesn't disclose any other behavioral aspects such as return format, error handling, or permissions needed.

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, concise sentence that front-loads the action. It contains no unnecessary information, making it highly efficient.

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?

Despite a 6-parameter schema and no output schema, the description only provides a one-line summary. It doesn't explain how parameters relate or what 'contents' means in this context, leaving the agent without enough information to use the tool effectively.

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?

All 6 parameters have schema descriptions covering 100%, so the schema already documents them. The description adds no additional parameter-specific context, earning the baseline of 3.

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 clearly states the tool retrieves node contents in an ABAP repository tree, using a specific verb and resource. However, it doesn't explicitly distinguish it from similar sibling tools like objectStructure or searchObject, so it falls short of a 5.

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. It doesn't mention any prerequisites, exclusions, or comparison with sibling tools.

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

Deploy Server