Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bw_replication_replicate_full

Pre-checks configuration, then triggers full replication of a datasource from a source system.

Instructions

One-stop: pre-check → trigger replication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activateNo
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.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the tool performs a pre-check and then triggers replication, which implies a mutating/executing action, but it does not explain side effects, whether the trigger runs synchronously, what the pre-check actually validates, or what happens on check failure.

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 extremely short and front-loads the core workflow with a clear arrow notation. There is no wasted text. Its brevity is an asset structurally, though it sacrifices substance in other dimensions.

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?

Given the tool has 5 parameters, no annotations, and no output schema, the description is insufficient for correct invocation. It explains neither the meaning of the optional parameters nor what 'pre-check' entails, leaving an agent to guess at required semantics and post-trigger expectations.

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

Parameters1/5

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

Schema description coverage is only 20% (only outputPath is documented), and the tool description provides no parameter explanations at all. sourceSystem, datasource, activate, and background are left entirely to inference, so the description fails to compensate for the low schema coverage.

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 states a clear purpose: perform a pre-check and then trigger replication. It is specific about the workflow and differentiates itself as a 'one-stop' combined operation, which separates it from the sibling bw_replication_replicate that likely only triggers. However, it does not name that sibling explicitly.

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 phrase 'One-stop: pre-check → trigger replication' implies when to use this tool: when the user wants both validation and execution in a single call rather than separate steps. However, it gives no explicit when-not-to-use guidance and does not identify alternatives such as bw_replication_info or bw_replication_replicate.

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