Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun

bw_trfn_auto_map_and_save

Automatically maps fields with identical names from source to target in a transformation, then saves and activates it.

Instructions

Atomic edit: auto-map same-named source→target fields in a transformation and save+activate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
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

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and must disclose behavioral consequences. It does mention 'atomic' and the save+activate side effect, but it does not describe overwrite behavior, prerequisites, effect on existing mappings, activation semantics, or the response shape.

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 concise and front-loaded, using one direct sentence with no filler. However, it is so abbreviated that it sacrifices important semantic details about parameters and usage, which limits its practical value.

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

Completeness1/5

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

Given 5 parameters, no annotations, no output schema, and minimal schema coverage, the definition is far from complete. An agent needs parameter semantics, usage guidance, and behavioral details to invoke the tool correctly, none of which the description supplies.

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%, so the description must compensate for the undocumented parameters. The description does not explain the required id, autoActivate, transport, or transportDescription, leaving an agent unable to determine what values to supply.

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 names a specific operation: auto-mapping same-named source→target fields in a transformation and then saving plus activating it. This is distinguishable from siblings like bw_trfn_add_rules_and_save and bw_trfn_save_and_activate, though 'source→target fields' remains somewhat ambiguous without more context.

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 guidance on when to prefer this tool over closely related siblings such as bw_trfn_add_rules_and_save, bw_trfn_set_end_routine_fields, or bw_trfn_save_and_activate. It implies a use case (same-named field auto-mapping) but does not state prerequisites, exclusions, or alternative conditions.

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