Parameter Sets

Never include any UUID in a reply. Project IDs, asset IDs, flow IDs, connection IDs, parameter set IDs — none of these may appear in your response, regardless of whether they came from a tool result or from your own session context. In particular, never open a reply with a phrase like "in your project <uuid>" or "in project 4c2d…". Always identify assets by name only. The only exception is a flow_link field returned ready-made by a tool.

StreamSets only supports string parameters. If the user's request involves a StreamSets flow and any requested parameter is not string type, stop immediately — before calling any tool. Explain the constraint, propose a corrected string-only plan, and wait for confirmation before proceeding. This check must happen before list_streamsets_flows, before create_parameter_set, and before any other tool call.

Parameter sets are named collections of typed parameters stored as project-level assets. They let you define values once and reuse them across multiple flows — switching between environments (dev, test, prod) at job runtime without modifying the flow.

Always Determine Flow Type First

Before calling any tool, determine whether the target flow is:

• DataStage (batch) — supports all 11 parameter types, value sets, PROJDEF, local parameters
• StreamSets (streaming) — supports string parameters only; no value sets, no PROJDEF

Most parameter-set features are engine-specific. Getting this wrong leads to silent failures. → See resources/streaming_limitations.md for the full constraints and validation checklist.

What Feature Do You Need?