Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Create Node from External Schema

create_node_from_external_schema

Automates node creation by reconciling predecessor columns with an external target schema, matching by name, adding new columns, dropping extras, and overriding data types.

Instructions

Create a workspace node whose output columns match an external table schema (e.g., from Snowflake DESCRIBE TABLE, dbt manifest, or any metadata source).

This tool automates the workflow of:

  1. Creating a node from predecessor(s) (auto-populates columns from source)

  2. Reconciling auto-populated columns against the external target schema

  3. Replacing columns to match the external schema exactly

Reconciliation logic:

  • Matched columns (by name): Preserves source linkage from predecessor, overrides dataType to match external schema

  • New columns (in target but not predecessor): Added without source mapping, flagged as needing a transform

  • Dropped columns (in predecessor but not target): Removed from the node

The response includes a reconciliation object showing exactly what was matched, added, dropped, and which types changed.

REQUIRED: Call plan_pipeline first to discover the correct nodeType.

Args:

  • workspaceID (string, required): The workspace ID

  • nodeType (string, required): Node type from plan_pipeline

  • predecessorNodeIDs (string[], required): One or more predecessor node IDs

  • targetColumns (array, required): External column definitions to match

  • targetName (string, optional): Name for the new node (e.g., 'STG_ORDER_HEADER')

  • locationName (string, optional): Storage location name

  • repoPath (string, optional): Local repo path for config completion

  • goal (string, optional): Intent for node type validation

Returns: { node, reconciliation: { matched, added, dropped, typeChanges }, predecessors, validation, configCompletion?, configCompletionSkipped?, nodeTypeValidation?, nextSteps }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoThe goal or intent for this node. Used to validate the chosen nodeType.
nodeTypeYesThe type of node to create. Call plan_pipeline first to discover and rank available node types.
repoPathNoPath to local Coalesce repository for automatic config completion.
targetNameNoName for the new node (e.g., 'STG_ORDER_HEADER'). If omitted, uses the auto-generated name from Coalesce.
workspaceIDYesThe workspace ID
locationNameNoStorage location name for the new node.
targetColumnsYesExternal column definitions describing the target table schema. Each column specifies name, dataType, and optionally nullable, description, and transform.
predecessorNodeIDsYesOne or more predecessor node IDs to link to the new node

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIDNo
createdNo
warningNo
nextStepsNo
validationNo
joinSuggestionsNo
configCompletionNo
nodeTypeValidationNo
configCompletionSkippedNo
Behavior5/5

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

The description details the reconciliation logic (matched, added, dropped, typeChanges) which goes beyond the annotations. It also clarifies that the tool is a write operation (not read-only) and is not destructive. No contradictions with annotations.

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 well-structured with a clear summary, workflow breakdown, and required prerequisite. It is slightly long but each section adds necessary value. Front-loaded with purpose.

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

Completeness5/5

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

Given the complexity (8 parameters, prerequisite, reconciliation logic), the description covers workflow, reconciliation, prerequisite, and response structure comprehensively. Output schema is mentioned.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds extra context for `goal`, `nodeType` (prerequisite), and `targetColumns` (auto-mapping, transform behavior), improving meaning beyond schema.

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 clearly states the tool creates a workspace node that matches an external table schema. It gives specific use cases (Snowflake DESCRIBE TABLE, dbt manifest) and distinguishes from sibling tools like `create_workspace_node_from_predecessor` and `create_workspace_node_from_scratch` by emphasizing external schema matching.

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 explicitly requires calling `plan_pipeline` first and explains the reconciliation logic. However, it does not explicitly mention when not to use this tool or list alternatives beyond the sibling tools.

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