Skip to main content
Glama
Sign In
coalesce-transform-mcp

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

COA List Project Nodes

coa_list_project_nodes
Read-onlyIdempotent

List all nodes defined in a local COA project before deployment. Get pre-deploy node details for project analysis and preparation.

Instructions

List all nodes defined in a local COA project (pre-deploy). Wraps coa create --list-nodes.

Different from list_environment_nodes (which lists deployed nodes in a cloud environment via the REST API).

Args:

  • projectPath (string, required)

  • workspace (string, optional)

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectPath": "<projectPath>"
    },
    "name": "coa_list_project_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

NameRequiredDescriptionDefault
jsonNo
stderrYes
stdoutYes
commandYes
exitCodeYes
timedOutYes
coaVersionYes
jsonParseErrorNo
preflightWarningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds operational detail: wraps a command and returns a specific structure. No contradictions and adds value beyond 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?

Description is concise, uses bullet points for args/returns, and front-loads the core purpose. No unnecessary words.

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 purpose, usage differentiation, returns structure, and parameter list. With full schema and annotations, the description is adequate. Could add more about the command context but not necessary.

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 covers both parameters with descriptions. Description merely restates parameter names and types without adding new context. Baseline 3 is appropriate given high schema coverage.

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 'List all nodes defined in a local COA project (pre-deploy)', providing a specific verb and resource. Distinguishes from sibling list_environment_nodes by specifying scope (local vs deployed).

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?

Explicitly differentiates from list_environment_nodes and states it is for pre-deploy listing. Gives clear context for when to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools