Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

COA Remove Warehouse Sources (delete scaffolded YAML)

coa_remove_warehouse_sources
Destructive

Delete scaffolded source-node YAML files from a Coalesce project to clean up after schema renames or re-onboarding. Requires confirmation and accepts a location filter or all sources.

Instructions

Delete scaffolded source-node YAML files from the project. Wraps coa sources remove --json --yes (the MCP layer handles confirmation; --yes is always passed to the CLI).

DESTRUCTIVE: removes files from disk. Requires confirmed: true. Hand-renamed ("unmanaged") files are reported but NOT removed — the CLI considers them user-owned.

MUST pass exactly one of location or all.

PROFILE LIMITATION: unlike list/add, the underlying coa sources remove does NOT accept a --profile flag in COA 7.35 (errors unknown option '--profile'). Profile resolution falls back to [default] in ~/.coa/config. If that diverges from the agent's intended profile, the agent should temporarily set [default] or wait for the upstream patch.

Usage pattern: when re-onboarding a location or cleaning up after a schema rename. Pair with coa_list_warehouse_sources to confirm scope first.

Args:

  • projectPath (string, required)

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

  • include (string, optional): glob filter (e.g. 'OLD_*')

  • confirmed (boolean): must be true to execute

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Highlights destructive nature, confirmation requirement, CLI wrapper behavior, and profile limitation, adding context beyond annotations. However, the parameter contradiction with schema reduces clarity.

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?

Well-structured with clear sections and front-loaded purpose. Slightly verbose but each sentence adds value. Could be more concise.

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?

Covers behavior, return shape, usage pattern, alternatives, and limitations. Lacks full alignment with input schema due to parameter mismatch, otherwise comprehensive.

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

Parameters1/5

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

Describes 5 parameters with detailed semantics, but the input schema declares no properties. This mismatch makes the parameter information unreliable and misleading, severely undermining usefulness.

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 'Delete scaffolded source-node YAML files from the project' with specific verb and resource. Distinguishes from sibling 'coa_list_warehouse_sources' by pairing suggestion.

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 when-to-use context (re-onboarding, cleanup after schema rename), required flags, profile limitation with workaround, and pairing with list tool. Covers when-not-to-use implicitly by noting unmanaged files are not removed.

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