Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Create Pipeline from Plan

create_pipeline_from_plan

Execute a pipeline by applying a previously approved plan from plan_pipeline. Confirm with a token to proceed.

Instructions

Create a Coalesce pipeline from a previously approved plan. Pass the exact plan object returned by plan_pipeline. Projection-capable node types execute by creating predecessor-based nodes first and then persisting the final full node body via set_workspace_node.

Args:

  • workspaceID (string, required): The workspace ID

  • plan (object, required): The exact plan object returned by plan_pipeline

  • confirmed (boolean, optional): Set to true after user approves the plan. Must be paired with confirmationToken

  • confirmationToken (string, optional): Token from prior STOP_AND_CONFIRM response. Required when confirmed=true

  • dryRun (boolean, optional): When true, validate without creating nodes

Returns: { created: boolean, nodes?: CreatedNode[], warnings?: string[] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYesThe plan object returned by plan_pipeline.
dryRunNoWhen true, validate the plan and return it without creating any nodes.
confirmedNoSet to true only after presenting the plan to the user and receiving explicit approval. Must be paired with the confirmationToken returned by the prior STOP_AND_CONFIRM response.
workspaceIDYesThe workspace ID
confirmationTokenNoThe token returned in the STOP_AND_CONFIRM response. Required when confirmed=true to prove the plan was presented to the user.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
planNo
errorNo
dryRunNo
reasonNo
createdNo
warningNo
cancelledNo
nodeCountNo
incompleteNo
workspaceIDNo
createdNodesNo
cleanupFailuresNo
STOP_AND_CONFIRMNo
failedPlanNodeIDNo
cleanupFailedNodeIDsNo
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds behavioral detail about projection-capable node types being created in two steps, which is useful beyond annotations. No contradiction found.

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 with a clear initial sentence and a parameter list. The list is somewhat lengthy but well-structured. Every sentence adds value, though the parameter section mirrors the schema.

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?

Given the complexity and presence of output schema, the description covers the main workflow: plan input, confirmation process, dryRun option, and return type. It could mention plan must be from plan_pipeline and status 'ready', but overall complete.

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?

Schema coverage is 100%, so the schema already describes all parameters thoroughly. The description repeats the parameter definitions without adding significant new meaning. The extra detail about projection-capable nodes is not parameter-specific.

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?

Description clearly states 'Create a Coalesce pipeline from a previously approved plan' with specific verb and resource. It distinguishes from siblings like plan_pipeline and build_pipeline_from_intent by specifying the input is the exact plan object.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says to pass the exact plan from plan_pipeline and requires user approval via confirmed and confirmationToken. It provides clear context for when to use but does not explicitly mention alternatives or when not to use. The confirmation token requirement adds strong usage guidance.

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/Coalesce-Software-Inc/coalesce-transform-mcp'

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