Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

List Job Nodes (grouped by subgraph)

list_job_nodes
Read-onlyIdempotent

Resolve a job's include/exclude selectors into concrete workspace nodes grouped by subgraph. Identify matched, unattached, and unresolved nodes to validate job configuration.

Instructions

Resolve a workspace job's selectors into concrete workspace nodes, grouped by subgraph. Composes getWorkspaceJob + listWorkspaceNodes + the local repo's subgraphs/ folder to evaluate the includeSelector/excludeSelector DSL (supported clauses: { subgraph: NAME } and { location: LOC name: NAME }, joined by OR).

Subgraph resolution note: the public Coalesce API has no subgraph list endpoint. { subgraph: NAME } terms can only be resolved when repoPath is set (or COALESCE_REPO_PATH). Without a repo, such terms land in unresolved and a warning is added to summary.warnings.

Args:

  • workspaceID (string, required): The workspace that owns the job

  • jobID (string, optional): The job ID. Preferred when known.

  • jobName (string, optional): The job name. Resolved against workspace jobs when jobID is absent.

  • repoPath (string, optional): Coalesce repo path for subgraph YAML lookup. Falls back to COALESCE_REPO_PATH or the coa profile.

Returns: { job: { id, name, includeSelector, excludeSelector }, summary: { totalNodes, subgraphCount, unattachedCount, unresolvedCount, warnings }, nodesBySubgraph: [{ subgraphID, subgraphName, nodes: [{ id, name, location, nodeType }] }], unattached: [...], // nodes matched by the job but not in any subgraph unresolved: [{ term, reason }] // selector terms that matched nothing (stale selectors or missing repoPath) }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobNo
summaryNo
unattachedNo
unresolvedNo
nodesBySubgraphNo
Behavior5/5

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

Annotations already declare readOnlyHint true, idempotentHint true, destructiveHint false. The description adds significant behavioral context: it composes multiple API calls, resolves a DSL, and details the subgraph resolution dependency on repoPath, including what happens without it (unresolved terms and warnings). 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.

Conciseness4/5

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

The description is well-structured with a summary, subgraph resolution note, Args, and Returns. It is moderately long but each sentence adds value. The key information is front-loaded. Minor verbosity in the DSL explanation is acceptable given complexity.

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?

Given the tool's complexity (DSL resolution, subgraph dependencies), the description is thorough: it explains the DSL clauses, repo path requirements, and provides a detailed output schema. Missing: the input parameters are not reflected in the actual input schema, but the description itself is complete for understanding usage and behavior.

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?

The input schema has 0 parameters, but the description lists four parameters (workspaceID, jobID, jobName, repoPath) with requirements and fallback behavior. This adds essential meaning that the schema lacks entirely. The description compensates fully for the absent schema parameter documentation.

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 resolves a workspace job's selectors into concrete nodes grouped by subgraph. The title 'List Job Nodes (grouped by subgraph)' reinforces this, distinguishing it from siblings like list_workspace_nodes (which lists all nodes) and get_workspace_job (which only gets job details).

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 explains when to use this tool—to resolve selectors—and details conditions like missing repoPath leading to unresolved terms. It mentions preferred arguments (jobID over jobName) and fallback behaviors, but does not explicitly contrast with alternative tools or provide explicit when-not-to-use guidance. Still, the context is clear and helpful.

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