Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

COA List Warehouse Sources

coa_list_warehouse_sources
Read-onlyIdempotent

List warehouse tables per storage location in a COA project. Shows summary counts or detailed table info with import status to identify un-imported tables or audit scaffolded sources.

Instructions

List warehouse tables visible to each storage location in a COA project. Wraps coa sources list --json.

Three modes via flags:

  • Neither location nor all: returns per-location SUMMARY counts (totalTables, importedTables, newTables). Cheap; use this first on unfamiliar projects.

  • location: <name>: returns per-table detail for that one location, each row marked alreadyExists: true if a source node has already been scaffolded for it.

  • all: true: per-table detail for every location. Potentially large — prefer scoping when you can.

Use this to (a) figure out which locations have un-imported tables before calling coa_add_warehouse_sources, or (b) audit which scaffolded source nodes still match the warehouse.

Read-only: queries the warehouse via the COA cloud profile, writes nothing. Profile resolution: input profile > COALESCE_PROFILE env > [default].

Args:

  • projectPath (string, required)

  • location (string, optional)

  • all (boolean, optional): mutually exclusive with location

  • include (string, optional): glob filter on table names

  • profile (string, optional)

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only and non-destructive behavior. The description reinforces this with 'Read-only: ... writes nothing' and adds useful context about profile resolution. No contradictions.

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?

The description is well-structured, front-loaded with the core function, followed by modes, usage guidance, behavioral notes, and parameter list. Every sentence adds value without redundancy.

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?

Overall comprehensive for a list tool: covers modes, usage, behavior, and returns. However, the return structure is only partially described (e.g., 'json?' is vague) and the actual output shape for details is not specified.

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 input schema is empty, so the description carries full parameter information. It lists five parameters with types and notes mutual exclusivity of 'location' and 'all'. However, it lacks format details for parameters like location or profile.

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's main function: listing warehouse tables visible to storage locations in a COA project. It distinguishes itself from sibling tools by explicitly referencing coa_add_warehouse_sources and explaining how this tool is used as a precursor.

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?

The description provides explicit guidance on when to use each of the three modes (summary first, location-specific for detail, all mode cautiously) and gives concrete use cases like identifying un-imported tables before adding sources.

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