Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun

bw_table_get_data

Retrieve SAP BW DDIC table data using OpenSQL SELECT via ADT data-preview. Use outputPath to write large result sets to a file.

Instructions

Query DDIC table data via the ADT data-preview service (OpenSQL SELECT). maxRows defaults to a small value and is capped to avoid huge inline payloads; for large reads set outputPath to dump the full result to a file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYesDDIC table name.
columnsNoOptional column allowlist. If omitted, all columns are read.
maxRowsNoMax rows to fetch (default 50).
orderByNoOpenSQL ORDER BY clause, without the ORDER BY keyword.
outputPathNoIf provided, the full result is written to this path (under the workdir) and the tool returns only a small summary envelope { ok, outputPath, bytes, summary }. Objects/arrays are written as JSON; ONLY the bw_*_get_xml family writes the raw XML string as plain text (that file is directly reusable as xmlPath in a later save call). Other *_get tools (e.g. bw_dtp_get, bw_trfn_get) write the PARSED XML-to-JSON tree, not raw XML — use the matching bw_*_get_xml tool when you need the raw XML string. Use outputPath for large responses (XML, table data, logs, dataflow graphs). When set, tools skip inline pagination/projection so the file contains the complete payload.
whereClauseNoOpenSQL WHERE clause, without the WHERE keyword. ⚠️ Executed with the configured BW credentials — avoid untrusted input.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are present, so the description carries the behavioral disclosure burden. It discloses the ADT data-preview backend, the maxRows cap motivation, and the outputPath escape hatch for large payloads. It does not mention response format or auth requirements, but the main read-only behavior and payload limits are clearly surfaced.

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 two compact sentences with no filler. It front-loads the core purpose and then adds the most important behavioral caveat. Every clause earns its place.

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 rich parameter schema covers all six parameters, but there is no output schema and the description does not specify the inline response format when outputPath is not used. The outputPath parameter description clarifies the file-writing summary envelope, but the default return payload shape is left implicit.

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 baseline is 3. The description adds a little context by explaining that maxRows defaults small and outputPath is intended for large reads, but these details also appear in the schema. It does not significantly deepen parameter understanding for table, columns, orderBy, or whereClause beyond the schema.

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?

The description identifies a specific operation: querying DDIC table data via the ADT data-preview service using OpenSQL SELECT. It clearly names the resource and the action. However, it does not explicitly differentiate itself from the sibling bw_table_query_sql, which could be a near alternative.

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 gives practical guidance about maxRows default/cap and recommends outputPath for large reads. It does not mention when to prefer this tool over siblings like bw_table_describe or bw_table_query_sql, so exclusions and alternative routing are missing.

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