Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bw_system_info

Retrieves SAP BW system information and capabilities for the current environment. Auto-logs in on first call and writes full results to a specified output path.

Instructions

Query BW system info and capabilities for the current environment (auto-logs in on first call). Use outputPath for the full document. For a single property or capability check, read the returned document (or buffered file) rather than separate tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries more behavioral responsibility and does disclose a real side effect: auto-login on first call. However, it does not state whether the operation is strictly read-only, what permissions are involved, or what happens on repeated calls, so transparency is only partial.

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 description is short and front-loaded, moving from purpose to usage notes in three sentences. The second sentence partially repeats the outputPath parameter description and 'separate tools' is vague, but the text remains economical and readable.

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?

Given one optional parameter, no output schema, and no annotations, the description covers auto-login, use of outputPath, and how to read a single property. It does not describe the default return payload or distinguish the tool from bw_system_status, so an agent may still be uncertain about exact output and tool selection.

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 coverage is 100% and the only parameter (outputPath) is already fully described in the schema. The main description adds only a brief recommendation to use outputPath for full documents, providing no new parameter-level meaning beyond the baseline.

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 verb ('Query') and resource ('BW system info and capabilities') scoped to 'the current environment', so the tool's purpose is clear. It does not explicitly contrast sibling bw_system_status, leaving some differentiation to inference from the name.

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 gives clear practical guidance: use outputPath for the full document and read the returned document for single property/capability checks rather than separate tools. It lacks a named alternative or explicit when-not-to-use conditions, but the provided context is actionable.

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

Deploy Server

Other Tools