Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetObjectStructureLow

Retrieve an SAP ADT object's structure as a compact JSON tree to inspect classes, programs, packages, or CDS views. Reuse a session to keep the same ADT context.

Instructions

[low-level] Retrieve ADT object structure as compact JSON tree. Returns XML response with object structure tree. Can use session_id and session_state from GetSession to maintain the same session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailNoHow much of the answer to return: "terse" (default, the fields you need to act), "full" (the whole parse), "raw" (the document as ADT sent it).terse
session_idNoSession ID from GetSession. If not provided, a new session will be created.
object_nameYesObject name
object_typeYesObject type (e.g., "CLAS/OC", "PROG/P", "DEVC/K", "DDLS/DF")
session_stateNoSession state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv16.0.0
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "terse",
+  "description": "How much of the answer to return: \"terse\" (default, the fields you need to act), \"full\" (the whole parse), \"raw\" (the document as ADT sent it).",
+  "enum": [
+    "terse",
+    "full",
+    "raw"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / object_name / description
      Previous value: -"Object name (e.g., \"ZMY_CLASS\", \"ZMY_PROGRAM\")"New value: +"Object name"
  2. First observed

TDQS

C2.6/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 disclosure burden. It mentions session reuse but does not state permissions required, whether a new session is implicitly created (schema hints this but description omits the behavior), or clarify the conflicting JSON/XML output claim.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences are front-loaded with the '[low-level]' tag, which is good structure. However, the second sentence's JSON-vs-XML contradiction wastes a line and actively confuses rather than informs.

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

Completeness3/5

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

No output schema exists, so the description would ideally describe the actual return shape, but it instead gives a contradictory one. For a read tool with a nested session_state object, it is minimally adequate but leaves the meaning of 'low-level' and the true response format unresolved.

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 five parameters, including the detail enum and session fields. The description adds only a light restatement of the session_id/session_state linkage, which is baseline-level value at most.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Retrieve ADT object structure') and flags itself as '[low-level]', but it does not differentiate from the sibling GetObjectStructure, so an agent cannot tell when 'Low' applies. It also self-contradicts on output ('compact JSON tree' vs 'Returns XML response'), which muddies the purpose.

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?

There is no when-to-use guidance and no comparison against the obvious alternative, GetObjectStructure (or GetNodeStructureLow). The only conditional hint is about reusing session_id/session_state, which is a continuity note rather than usage routing.

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