Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

bw_create_dtp

Create and activate a DTP for an existing transformation. Supports single-step and two-step chains; optionally filter on a source field.

Instructions

Create a new DTP (Data Transfer Process) for an existing Transformation and activate it. The DTP name is server-generated. Optionally set a filter on one source field (Equal operator). After creation the DTP is activated automatically. IMPORTANT: Before calling this tool, always check the full transformation chain. Single-step chain (e.g. ADSO->ADSO): use trfn_name only. Two-step chain (e.g. ADSO->TRCS->ADSO): use trfn_name for the first transformation and trfn_name_2 for the second; source_name/source_type = the start object, target_name/target_type = the end object. Omitting trfn_name_2 in a two-step chain causes a persistent HTTP 500 error. Use bw_get_transformation or bw_xref to determine the chain before creating the DTP. DataSource source: set source_type "RSDS" and pass source_system (the DataSource source system). source_name is then the plain DataSource name; the tool builds the RSDS compound source key internally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNoDevelopment package (default "$TMP").
trfn_nameYesTechnical name of the existing Transformation (UUID-like key).
descriptionNoOptional DTP description text (default: empty).
source_nameYesSource object name (e.g. "SOURCE_NAME").
source_typeYesSource object type (e.g. "ADSO", "TRCS", "RSDS"). Use "RSDS" for a DataSource source — source_system is then required.
target_nameYesTarget object name (e.g. "TARGET_NAME").
target_typeYesTarget object type (e.g. "ADSO"). Use "IOBJ" to load into an InfoObject's attributes (encoded server-side as IOBJA). InfoObject text/hierarchy targets (IOBJT/IOBJH) are not yet supported.
trfn_name_2NoOptional second transformation in a multi-step chain. Include when the DTP spans two transformations (e.g. ADSO→TRCS→ADSO).
filter_fieldNoField name to filter on. Requires filter_dta_name and filter_value.
filter_valueNoFilter value for the Equal selection (e.g. "PL_001").
source_systemNoSource system name of the DataSource. Required when source_type is "RSDS".
filter_dta_nameNoInternal dtaName for the filter field.

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

With no annotations, the description adequately discloses the tool's behavior: creates and activates a DTP, with server-generated naming and optional filter. It warns of persistent HTTP 500 errors if misused. However, it does not mention authorization requirements, idempotency, or side effects like overwriting existing DTPs.

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?

The description is front-loaded with the main purpose and structured logically, covering chain variants, special cases, and error prevention. Every sentence provides necessary information with minimal redundancy.

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?

The description thoroughly covers input parameters and usage scenarios, including common pitfalls. However, it does not describe the tool's return value (e.g., created DTP name or success message), which would be helpful given the lack of an output schema.

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

Parameters5/5

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

Although the schema already describes all 12 parameters (100% coverage), the description adds significant value: explains the required relationship between source_type 'RSDS' and source_system, the encoding of target_type 'IOBJ' as IOBJA, and the logic for trfn_name vs trfn_name_2 based on chain structure. This goes well beyond the schema's individual field 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 tool creates and activates a DTP for an existing transformation. It specifies server-generated naming and optional filtering, distinguishing it from sibling tools like bw_get_dtp and bw_update_dtp.

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?

The description provides explicit when-to-use guidance: checking transformation chain length, using trfn_name_2 for two-step chains, special handling for DataSource sources, and warnings about HTTP 500 errors. It also names alternative tools (bw_get_transformation, bw_xref) for pre-checking.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dnic-dev/bw-modeling-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server