Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun

bw_replication_replicate

Run SAP BW DataSource replication with explicit pre-check tasks and a configurable activation strategy, optionally in background and with full output written to a file.

Instructions

Trigger DataSource replication with explicit pre-check tasks. activate is a strategy string (not a boolean).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYesReplication tasks.
activateNoActivation strategy value.
backgroundNo
datasourceYes
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.
sourceSystemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.5/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Trigger DataSource replication' and clarifies the activate type, but says nothing about side effects, permissions, reversibility, or what happens on failure. This is a significant gap for a replication-triggering tool.

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 a single sentence with no fluff. It front-loads the main purpose and adds one parameter clarification. It is appropriately concise, though it sacrifices content for brevity.

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

Completeness2/5

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

For a tool with 6 parameters, 3 required, and no annotations, the description is severely incomplete. It doesn't explain the tasks array structure, the meaning of activate strategies, or how this tool relates to bw_replication_replicate_full. The outputPath behavior is documented in the schema but not in the description, and the description leaves too much for the agent to infer.

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

Parameters2/5

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

Schema coverage is 50%, so the description should compensate for undocumented parameters like sourceSystem, datasource, and background, but it does not. The one clarification about activate ('strategy string, not boolean') adds a little value, but it's redundant with the schema's type and doesn't explain how to choose values. The description fails to compensate for the coverage gap.

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 clearly states the action (Trigger DataSource replication) and adds a distinguishing detail (with explicit pre-check tasks). It does not explicitly name the sibling bw_replication_replicate_full, so it could be sharper, but the core purpose is clear.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use this tool versus alternatives like bw_replication_replicate_full. The only hint is the mention of 'explicit pre-check tasks,' but it doesn't explicitly state when that matters or when to choose the other tool. No exclusions or prerequisites are given.

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