bw-modeling-mcp

bw_xref

Find which transformations, DTPs, process chains, and aggregation levels reference a given SAP BW object. Returns source, target, and direction to trace data flow.

Instructions

Find where-used / dependencies for a BW object. Returns all objects that reference the given object. Use this to find the Transformation and DTPs that reference an aDSO, or to find which DTPs depend on a Transformation. Every transformation and DTP hit carries its source and target (type and name) and its direction relative to the object: upstream (feeds it) or downstream (fed from it) — follow upstream hits hop by hop to trace a data flow back to its DataSource. On classic SAP BW the analysis processes that write to or read from a provider (ADSO, ODSO, CUBE, MPRO, IOBJ) are listed too, with direction. On every release the aggregation levels built on a provider are listed as upstream (planned values are written into the provider through them), and object_type=ALVL lists the InfoProvider underneath (downstream) and the planning functions on the level (upstream) next to its queries. Use object_type=DTPA to find the process chain(s) a DTP belongs to — this is preferred over bw_get_dtp when only the process chain is needed.

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_type": "<object_type>",
      "object_name": "<object_name>"
    },
    "name": "bw_xref"
  }
}

Input Schema

Name	Required	Description
`object_name`	Yes	Object name (e.g. "ADSO_NAME" or "TRFN_UUID_KEY").
`object_type`	Yes	Object type: ADSO, TRFN, DTPA, IOBJ, etc.
`source_system`	No	Required for object_type "RSDS". Logical source system name (e.g. "LSYS_NAME"). The correct padded objectName is built automatically.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0May 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so in detail: it explains that transformation and DTP hits carry source, target, type, name, and upstream/downstream direction, and it discloses special listings for analysis processes, aggregation levels, objects beneath an ALVL, and planning functions. It also clarifies how to trace data flow hop by hop, which is substantive return/payload context beyond structured fields.

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 purpose and primary use case are front-loaded in the first two sentences, and the remaining detail is relevant to this complex tool. The description is long and formatted as a single dense paragraph rather than structured sections, which slightly reduces skimmability.

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

Completeness5/5

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

Given no output schema and no annotations, the description is complete enough: it explains what the tool returns, how to interpret direction, special object-type behaviors, and the preferred alternative for DTP-to-process-chain lookups. It covers the complex xref semantics an agent needs to invoke and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning for object_type values such as ALVL and DTPA beyond what the schema alone conveys. It does not specifically clarify source_system behavior, which remains schema-only.

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 states a specific verb and resource: find where-used/dependencies for a BW object, returning all referencing objects. It distinguishes itself from siblings by naming bw_get_dtp and explaining when this tool is preferred. An agent can identify the tool's scope without opening the schema.

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?

It gives explicit usage contexts—finding transformations and DTPs for an aDSO, tracing DTP dependencies, and using object_type=DTPA for process chains—and names bw_get_dtp as an alternative for that last case. It also describes special handling for classic SAP BW and aggregation levels, providing clear routing guidance.

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

Deploy Server