Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bw_dtp_create

Create an inactive Data Transfer Process (DTP) between two ADSOs with a bound transformation, then configure and activate it for full or delta extraction.

Instructions

Create a DTP via the generic object POST flow (CREA lock + collection POST). Body is minimal (extractionSettings + overview TRFN binding + source/target); the server hydrates filter fields and program flow. Created DTP is inactive — configure (extractionMode/filter via get_xml → edit → save_and_activate) then activate. Note: DTP filters cannot express empty-value comparisons; encode them as selections without a element ( = not-initial).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoDTP id; omit to auto-generate (DTP_ET0916OM0D + 16 random chars).
transportNoWorkbench request number.
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.
sourceNameYesSource ADSO name.
targetNameYesTarget ADSO name.
descriptionNo
packageNameNoTarget package, default $TMP.
transformIdYesBound transformation (TRFN) id.
extractionModeNoF=full (default), D=delta.

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 carries the full burden. It discloses that the body is minimal and the server hydrates fields, that the created DTP is inactive, and a key limitation about filters (cannot express empty-value comparisons). This is substantial behavioral context, though it does not cover permissions or error behavior.

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, each earning its place: the first defines the core action and flow, the second explains the post-creation lifecycle, and the third notes a critical filter encoding limitation. No redundant wording; information is front-loaded.

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?

For a create tool with a rich schema (89% coverage) and no output schema, the description covers the creation flow, the inactive state, and a key filter constraint. It does not describe the return value, but the outputPath parameter in the schema partially addresses response handling. Overall, adequate for an agent to call correctly.

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

Parameters4/5

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

Schema coverage is high (89%), so the baseline is 3. The description adds value by clarifying that the body is minimal and the server hydrates filter fields, emphasizing that sourceName, targetName, and transformId are the core required parameters. This goes beyond the schema's per-parameter descriptions.

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?

The description clearly states the verb 'Create' and resource 'DTP', and specifies the underlying flow ('generic object POST flow (CREA lock + collection POST)'). It is unambiguous and distinct from sibling tools like bw_dtp_check or bw_dtp_execute by focusing on creation.

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?

Provides a clear workflow: after creation, the DTP is inactive and requires configuration (extractionMode/filter via get_xml → edit → save_and_activate) then activation. This implies when to use this tool (initial creation) versus later configuration tools, though it does not explicitly name alternatives or state exclusions.

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