Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bw_trfn_set_end_routine_fields

Checks specified target fields into a transformation's end routine, then saves and activates it. Ensures the routine includes the required fields for execution.

Instructions

Check a list of target field names into the transformation's end routine and save+activate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
fieldsYesTarget field names to check into the end routine.
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.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden; it does explicitly disclose that the operation saves and activates the transformation, which is a key side effect. It does not clarify whether existing end-routine content is overwritten or appended, what permissions are needed, or what response is returned.

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?

A single short sentence with no filler, and the core action plus side effect appear early. The wording is slightly awkward ('Check ... into') but the structure is appropriately lean.

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?

For a six-parameter tool with no annotations and no output schema, a one-clause description is inadequate. It omits the role of id, autoActivate defaults, transport semantics, return behavior, and how this differs from the surrounding bw_trfn_* save/activate tools.

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

Parameters2/5

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

The only parameter the description touches is fields ('target field names'), and even that merely restates the schema description. With schema coverage at 33%, the description was expected to explain id, transport, outputPath, autoActivate, and transportDescription, but it does not.

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 concrete action — checking a list of target field names into the transformation's end routine — and adds the persistence side effect 'save+activate'. This is specific enough to set it apart from generic transformation save tools, though the word 'Check' is slightly ambiguous.

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?

No guidance is given about when to choose this tool over siblings such as bw_trfn_add_rules_and_save, bw_trfn_auto_map_and_save, or bw_trfn_save_and_activate. There are no prerequisites, exclusions, or alternative conditions; usage is only implied by the action described.

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