mcp-abap-abap-adt-api

nodeContents

Read-only

Lists the direct contents of an ABAP package or function group, showing its immediate child nodes. Use it to inspect a repository level; for source code, use the dedicated package tree or function group tools.

Instructions

One level of the repository tree: what is directly inside a package, or inside a function group. Two things to know. Most rows hand back a SAPGUI bridge URI that serves properties and no content, so it is not the way to read sources - packageTree resolves the real source URLs, and listFunctionGroup does it for a group. And an unknown package answers exactly like an empty one, with no nodes at all, so only a repository search tells them apart.

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
`user_name`	No	The user name.
`parent_name`	No	The name of the parent node.
`parent_type`	Yes	The type of the parent node.
`parentnodes`	No	An array of parent node IDs.
`rebuild_tree`	No	Whether to rebuild the tree.
`parent_tech_name`	No	The technical name of the parent node.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: most rows return a SAPGUI bridge URI with properties but no content, and unknown packages return no nodes (indistinguishable from empty). This goes beyond the annotations and helps the agent set expectations.

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?

The description is compact and front-loaded with the core purpose ('One level of the repository tree'). The two caveats are important and each sentence earns its place. Slightly verbose phrasing ('Two things to know') but overall efficient.

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 read-only tree-navigation tool with full schema coverage and no output schema, the description covers the key behavioral quirks (bridge URIs, unknown-package behavior) and routes to alternatives. It doesn't describe the exact response shape, but no output schema exists and the annotations cover safety. The main gap is not explaining what 'parent_type' values are valid, but the schema already names the field.

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 schema already documents all six parameters. The description does not add parameter-level detail beyond the schema, but it does clarify the meaning of 'parent' in context (package or function group). Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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 returns one level of the repository tree (contents of a package or function group), which is a specific verb+resource. It distinguishes itself from packageTree and listFunctionGroup by noting they resolve real source URLs, but it doesn't explicitly name all sibling tools that might overlap (e.g., objectStructure, searchObject).

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

Usage Guidelines5/5

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

The description explicitly tells the agent when NOT to use this tool: it is not the way to read sources, and packageTree/listFunctionGroup are the alternatives for resolving real source URLs. It also warns that an unknown package looks like an empty one, so a repository search is needed to distinguish them. This is strong when-to-use vs alternatives guidance.

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

Deploy Server