Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun

bw_reporting_initial_view

Fetch the initial reporting view for an SAP BW provider, returning metadata, default axes, and result set. Specify outputPath to write large payloads to a file instead of inline.

Instructions

GET BICS initial reporting view for an ADSO / InfoObject / Composite Provider (compid !NAME). Returns metadata (characteristics, key figures, ids), default axes, and result set. Prefer outputPath — payloads are large. For axis remapping use bw_reporting_preview instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toRowNoResult-set end row inclusive (default ~1000 on server).
fromRowNoResult-set start row (default 0).
providerYesProvider technical name, with or without ! prefix (e.g. ZL_FID09).
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.
inclMetadataNoInclude metadata (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description itself indicates a read-only GET operation, lists what it returns, and warns that payloads are large. It does not discuss permissions or failure behavior, but the key behavioral trait (large response) and the mitigation (outputPath) are present.

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 sentences, front-loaded with the core purpose, followed by two high-value usage notes. No filler or redundant restatement.

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?

Given the parameter schema covers all fields and the description covers purpose, return content, payload size, and the main alternative, the tool is callable without missing essential context. Without annotations or an output schema, slightly more detail about expected result size/pagination could be added, but it is not critical.

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 parameters are already documented. The description adds only contextual value about outputPath and provider prefixes, not a meaningful amount of new parameter semantics beyond the schema.

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?

States a specific verb (GET), resource (BICS initial reporting view), supported provider types (ADSO / InfoObject / Composite Provider), and the returned content (metadata, default axes, result set). It explicitly names bw_reporting_preview as the tool for axis remapping, making the distinction clear.

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?

Gives direct usage guidance: prefer outputPath because payloads are large, and use bw_reporting_preview instead when axis remapping is needed. This tells an agent when to choose this tool and when to route elsewhere.

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