Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetObjectStructure

Retrieve the structure of an SAP ADT object as a compact JSON tree. Provide object type and name; choose terse, full, or raw detail to inspect its fields.

Instructions

[read-only] Retrieve ADT object structure as a compact JSON tree.

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
objectnameYesADT object name (e.g. /CBY/ACQ_DDL)
objecttypeYesADT object type (e.g. DDLS/DF)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
+}
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No structured annotations are provided, so the description must carry the burden. It does disclose the read-only ([read-only]) safety profile and notes the output is a 'compact JSON tree', which is useful context, but it says nothing about depth/recursion behavior, error cases for invalid object types, or how 'structure' is bounded.

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?

A single front-loaded sentence with zero waste; the [read-only] tag is placed first and the core action follows immediately. Nothing could be trimmed without losing meaning.

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?

For a 3-parameter read-only retrieval with full schema coverage and no output schema, the description is adequate but thin: it does not clarify what the returned tree contains or how it relates to GetObjectStructureLow, leaving an agent to infer the distinction.

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%, including a well-documented enum (terse/full/raw) and examples for objecttype/objectname, so the schema does the heavy lifting. The description adds no parameter meaning beyond what the schema already provides, which is the baseline 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?

States a specific verb (Retrieve) and resource (ADT object structure) plus the return shape (compact JSON tree), so the agent knows what it does. However, it does not distinguish itself from the near-identical sibling GetObjectStructureLow, nor from GetNodeStructureLow/GetStructure, leaving ambiguity about which retrieval to pick.

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, no prerequisites, and no mention of alternatives. An agent cannot tell from the text why it should call GetObjectStructure rather than GetObjectStructureLow or GetObjectInfo.

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