abap-adt-mcp

取得物件結構

get_object_structure

Retrieve the structure of ABAP objects including class methods, includes, and source URI to understand object composition.

Instructions

取得 ABAP 物件的結構資訊(class 的 methods/includes、program 的組成等)與 source URI。

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": {
      "object_url": "<object_url>"
    },
    "name": "get_object_structure"
  }
}

Input Schema

Name	Required	Description	Default
`object_url`	Yes	物件的 ADT URI,例如 /sap/bc/adt/oo/classes/zcl_demo

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 25, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It mentions retrieving structure info and source URI, but does not disclose any behavioral traits (e.g., read-only nature, auth requirements, side effects, rate limits). It adds minimal context beyond the purpose.

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 sentence that efficiently conveys the tool's purpose and key details. No unnecessary words or redundancy.

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?

The tool is simple with one parameter and no output schema. The description covers the basic function but could be more complete by elaborating on what 'structure information' includes (e.g., format, hierarchical details). Adequate but not exhaustive.

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?

The single parameter 'object_url' is fully described in the schema (100% coverage) with an example. The description adds no additional meaning beyond what the schema provides, so baseline score 3 is appropriate.

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

Purpose5/5

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

The description clearly states it retrieves structure information of ABAP objects, with specific examples like class methods/includes and program composition. This distinguishes it from siblings like read_source (source code) and browse_package (package browsing).

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

Usage Guidelines3/5

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

The description implies usage when one needs structure info and source URI, but does not explicitly state when to use this tool versus alternatives like read_source or search_objects. No guidance on when not to use.

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

Deploy Server