Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

COA Create (DDL)

coa_create
Destructive

Execute DDL CREATE/REPLACE statements for selected nodes in your data warehouse, with pre-flight validation and required user confirmation to prevent accidental schema modifications.

Instructions

Execute coa create — runs DDL (CREATE/REPLACE) for the selected nodes against the configured warehouse.

DESTRUCTIVE: modifies warehouse schema. Requires confirmed=true after explicit user approval.

Pre-flight checks run before execution (double-quoted refs, missing workspaces.yml, bad selector patterns). Errors block execution; warnings are returned alongside the result.

V2 NOTICE: when the project contains V2 artifacts (fileVersion: 2 node types or .sql nodes), a V2_DETECTED preflight warning attaches to the result. Execution is no longer blocked — annotation sync (CD-16972) and UNION ALL shipped in COA 7.35 closed the biggest V2 risks. Two rough edges remain: coa validate false positives on aliased columns, and zero-column CTAS when a SELECT has a parse error. See coalesce://context/sql-node-v2-policy.

Args:

  • projectPath (string, required)

  • workspace, include, exclude (optional)

  • confirmed (boolean): must be true to execute

Returns: { command, exitCode, stdout, stderr, preflightWarnings?, coaVersion }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
excludeNoCOA node selector to exclude.
includeNoCOA node selector, e.g., '{ STG_ORDERS }' or '{ location: "SRC" }'. See `coa describe selectors`.
confirmedNoSet to true after the user explicitly confirms. Without this, the tool returns a STOP_AND_CONFIRM response instead of executing.
workspaceNoCOA workspace name from workspaces.yml. Defaults to 'dev'.
projectPathYesAbsolute or relative path to the COA project root (the directory containing data.yml).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonNo
stderrYes
stdoutYes
commandYes
exitCodeYes
timedOutYes
coaVersionYes
jsonParseErrorNo
preflightWarningsNo
Behavior5/5

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

The description explicitly states DESTRUCTIVE: modifies warehouse schema, requires confirmation, and details pre-flight checks and V2 notice. This adds significant context beyond the destructiveHint annotation, which is already true.

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 structured with clear sections (DESTRUCTIVE, pre-flight, V2 NOTICE, Args, Returns) and front-loads the purpose. It is informative but could be slightly trimmed; however, it earns its length.

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 tool's destructive nature, 5 parameters, and output schema, the description covers behavior, required confirmation, preflight checks, V2 details, and return structure comprehensively. No gaps identified.

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?

The description adds meaning to parameters beyond the schema, e.g., explaining confirmed must be true to execute, and clarifying include/exclude selectors. Since schema coverage is 100%, the description still adds value.

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 executes 'coa create' to run DDL (CREATE/REPLACE) for selected nodes against the configured warehouse. It distinguishes itself from sibling tools like coa_dry_run_create by indicating destructive behavior and required confirmation.

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 provides clear context: requires confirmed=true after user approval, runs pre-flight checks, and notes V2 behavior. It does not explicitly mention when not to use or compare to alternatives, but the guidance is sufficient for appropriate use.

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