Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

COA Bootstrap workspaces.yml (doctor --fix)

coa_bootstrap_workspaces
Destructive

Generates a starter workspaces.yml for a Coalesce project from locations.yml. Confirmation needed before file is written.

Instructions

Run coa doctor --fix — writes a starter workspaces.yml in the project root, seeded from locations.yml. Safe to re-run; coa will not overwrite a valid existing file.

IMPORTANT: the generated file contains placeholder database/schema values. The user MUST open it and set real values before running coa_create / coa_run — otherwise warehouse operations will target non-existent databases.

KNOWN ISSUE (CD-16983): the workspaces.yml profile controls coa create/run, but coa plan/deploy/refresh fall through to [default] in ~/.coa/config. After bootstrap, check that the two profiles point at the same cloud account before relying on plan/deploy results.

DESTRUCTIVE: writes a new file to the project directory. Requires confirmed=true after explicit user approval.

Args:

  • projectPath (string, required): Path to the COA project root (directory with data.yml)

  • workspace (string, optional): workspaces.yml workspace name (default: dev)

  • confirmed (boolean): must be true to execute

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds behavioral context: it writes a file, is safe to re-run, includes a known issue about profile fall-through, and requires confirmed=true. This adds value beyond annotations without contradiction.

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 clear sections (main action, important notes, known issue, destructive warning, args, returns). Every sentence provides useful information, though it could be slightly more concise without losing clarity.

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 has 3 parameters, output schema, and side effects, the description covers purpose, usage warnings, known issues, destructive nature, and return format. It fully equips the agent to understand when and how to use the tool.

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 description coverage is 100%, so the schema already documents all parameters. The description does not add additional semantics beyond what the schema provides (e.g., confirmed requirement is also in schema). Baseline score of 3 is appropriate.

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 runs 'coa doctor --fix' to write a starter 'workspaces.yml' file, seeded from 'locations.yml'. The verb 'writes' and specific resource distinguish it from siblings like coa_doctor, coa_create, etc.

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 usage context: it is safe to re-run, will not overwrite existing valid files, and warns that placeholder values must be replaced before using coa_create/coa_run. It also mentions the known issue about profile configuration. It lacks explicit when-not-to-use or alternatives but provides strong guidance overall.

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