mcp-abap-abap-adt-api

abapPath

Read-only

Trace call paths between ABAP objects to determine if one object's code reaches another, following usage references breadth-first.

Instructions

Whether one object's code reaches another, and through what. Walks usageReferences backwards from "to" through its callers, breadth-first, until it reaches "from" or runs out of budget - the same data impactOf uses, just followed as a chain instead of rolled up one level. Pure ADT data, no ABAP parsing: a call made only dynamically (CALL METHOD (name)) is invisible to it, same as usageReferences itself.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "abapPath"
  }
}

Input Schema

Name	Required	Description
`toUrl`	No	ADT object URL for the target, for a type toName cannot address.
`toName`	No	Target object, e.g. ZCL_APP_RETURN. Use with toType.
`toType`	No	ADT type of toName. Defaults to CLAS/OC.
`fromUrl`	No	ADT object URL for the start, for a type fromName cannot address.
`fromName`	No	Starting object, e.g. ZR_APP_REPORT. Use with fromType.
`fromType`	No	ADT type of fromName. Defaults to CLAS/OC.
`maxDepth`	No	How many hops to try before giving up (default 8).
`maxNodes`	No	Total objects to fetch usageReferences for across the whole search before giving up (default 300). A widely used interface as an intermediate hop can otherwise turn this into a wide, expensive search.
`onlyCustom`	No	Only walk through Z, Y and /namespace/ objects (default true). A path through standard SAP code is rare and usually means the two objects are not really related.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already state readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety, and it still increases value by revealing non-obvious behavior: the traversal is breadth-first, budget-limited, and entirely based on ADT static data with no ABAP parsing. It explicitly calls out that dynamic CALL METHOD is invisible, a critical blind spot for the agent. These are behaviors not derivable from the annotations or schema, so the description carries its weight.

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?

Three dense, purposive sentences: what, how, and limitation. Every phrase earns its place—the impactOf comparison is a second reference, and the dynamic-call caveat is a valuable nuance. There is no filler or repetition of schema content, and the most operative detail comes first.

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 9-parameter tool with no output schema, the description covers the core algorithm, traversal budget, data-source purity, and a key missed edge case. It does not explicitly describe the shape of the returned path or result with no path found, but that is a moderate gap given the tool's complexity and absence of an output schema. Overall the description is complete enough for an agent to call it effectively and interpret the main semantics.

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 9-parameter schema has 100% description coverage, giving the baseline of 3. The description adds multi-dimensional context by explaining the budget-driven traversal and the 'same data as impactOf' relationship, which helps verify parameters like maxDepth and maxNodes. But it doesn't enumerate or simplify per-parameter semantics beyond what the schema already provides, so a 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 opens with a precise purpose, 'Whether one object's code reaches another, and through what,' which immediately distinguishes reachability analysis from simpler lookup tools. It further clarifies the method by stating it walks usageReferences backward from 'to' through callers, explicitly contrasting it with impactOf's roll-up approach. This leaves no ambiguity about what the tool does or which sibling it relates to.

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

Usage Guidelines4/5

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

The description implicitly tells the agent when to use this tool: when you need a specific 'from' to 'to' path through callers, rather than a rolled-up impact analysis. It references impactOf and usageReferences as the underlying data source, giving context, but it does not explicitly name alternatives or provide explicit when-not conditions. The mechanism is clear enough to infer the right call timing.

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

Deploy Server