Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

COA Add Warehouse Sources (scaffold source nodes)

coa_add_warehouse_sources
Destructive

Scaffold source-node YAML files from warehouse tables, reading database and schema from workspace config. Supports dry-run preview to list changes without writing.

Instructions

Scaffold source-node YAML files from warehouse tables. Wraps coa sources add --json. Database and schema are read from the workspace's storage-location config and copied onto each scaffolded source node — no separate placeholders to fix up afterward, but verify the workspace config itself is correct first (the bootstrap tool seeds placeholders into it).

DESTRUCTIVE: writes files into the project's nodes/ tree. Requires confirmed: true. Existing source nodes are skipped unless overwrite: true.

MUST pass exactly one of location or all (the CLI enforces this in non-TTY mode and so do we).

DRY-RUN: pass dryRun: true to list what would be imported without writing files. The JSON shape is the same as a real write, with wouldImport reflecting the delta. confirmed: true is still required for consistency, but no files are created.

Profile resolution: input profile > COALESCE_PROFILE env > [default].

Usage pattern: call coa_list_warehouse_sources --location <name> first to preview, then call this with the same scope.

Args:

  • projectPath (string, required)

  • location (string) OR all (boolean): exactly one required

  • include (string, optional): glob filter

  • overwrite (boolean, optional): re-import existing nodes

  • dryRun (boolean, optional): preview without writing

  • profile (string, optional)

  • confirmed (boolean): must be true to execute. Required even when dryRun: true, for consistency with other destructive tools — no files are written in that case.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond annotations (destructiveHint=true), description details that it writes files, requires confirmed:true, skips existing nodes unless overwrite:true, and explains dry-run behavior (no files written). No contradiction 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections, front-loaded purpose, and no unnecessary words. Every sentence adds value.

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?

Covers all aspects: destructive behavior, parameters, dry-run, profile resolution, return shape, and a usage pattern. No gaps given the tool's complexity.

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

Parameters5/5

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

Despite the input schema showing no properties, the description thoroughly explains each parameter (projectPath, location, all, include, overwrite, dryRun, profile, confirmed) and their roles, effectively compensating for the empty 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?

Clearly states the tool scaffolds source-node YAML files from warehouse tables, distinguishing itself from sibling tools like coa_remove_warehouse_sources and coa_list_warehouse_sources via a usage pattern mention.

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

Usage Guidelines5/5

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

Provides explicit usage constraints: exactly one of location or all, dry-run option, profile resolution, and a recommended pattern to preview with coa_list_warehouse_sources first.

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