Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun

bw_trfn_add_rules_and_save

Add source-to-target mapping rules to a SAP BW transformation, then save and activate it. Omit target for same-name mapping, or specify custom pairs.

Instructions

Atomic edit: add DIRECT mapping rules (source→target pairs) to a transformation and save+activate. target omitted means same-name mapping.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
rulesYesMapping rules to insert.
transportNo
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.
autoActivateNo
transportDescriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does communicate that this is a mutating, atomic operation that saves and activates, and it explains the same-name fallback when target is omitted. However, it does not disclose how existing rules are treated (merged vs replaced), what happens if activation fails, or what the tool returns.

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 two short, information-dense clauses with no filler. The core operation is front-loaded ('Atomic edit'), and the target-omission rule is stated efficiently.

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?

The core invocation is understandable, but with no output schema, no annotations, six parameters, and a large sibling family, the description is only minimally complete. It lacks guidance on selection, return value, failure behavior, and the role of autoActivate. The detailed outputPath semantics live in the schema, not the description, so the description itself leaves meaningful gaps.

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?

With only 33% schema description coverage, the description partially compensates by defining rules as source→target pairs and clarifying that omitting target means same-name mapping. It adds no meaning for id, transport, autoActivate, or transportDescription. The claim 'save+activate' may also conflict with the optional autoActivate boolean, creating ambiguity.

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 states a specific verb and resource: add DIRECT mapping rules (source→target pairs) to a transformation and save+activate. It distinguishes itself from related siblings like bw_trfn_auto_map_and_save by emphasizing 'DIRECT' mapping rules, and the 'target omitted means same-name mapping' detail adds precision.

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 gives no explicit guidance on when to use this tool versus alternatives such as bw_trfn_auto_map_and_save, bw_trfn_set_end_routine_fields, or bw_trfn_save_and_activate. The capitalized 'DIRECT' hints at a contrast with auto-mapping, but no alternatives, exclusions, or preconditions are stated.

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