Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

List Workspace Nodes

list_workspace_nodes
Read-onlyIdempotent

Lists nodes in a Coalesce workspace with pagination; returns one page with a cursor to fetch the next.

Instructions

List nodes in a Coalesce workspace (use list_workspaces to find workspace IDs). Returns ONE page (default 100 nodes, or 25 when detail=true).

IMPORTANT: if the response has hasMore: true, this is NOT the whole workspace — treating one page as complete will undercount it. Either page through the rest (call again with startingFrom set to the returned next, same orderBy), or better, switch tools: use analyze_workspace_patterns for a complete whole-workspace profile in one call, or search_workspace_content / get_workspace_node by ID to find specific nodes. Only page the full workspace when the user explicitly wants a full inventory.

Args:

  • workspaceID (string, required): The workspace ID

  • detail (boolean, optional): Include full node details

  • limit, startingFrom, orderBy, orderByDirection: Pagination (limit defaults to 100, or 25 when detail=true)

Returns: { data: Node[], next?: string, hasMore?: boolean, retrieved?: number }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (max 500)
detailNoInclude full node details in response
orderByNoField to sort by (required with startingFrom)
workspaceIDYesThe workspace ID
startingFromNoCursor from previous response's next field
orderByDirectionNoSort direction

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
nextNo
totalNo
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. The description adds specific pagination behavior (default limits, hasMore flag, page semantics) and warns about incomplete results. This 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?

Very concise: a single sentence for purpose, a clear warning, then a paragraph with usage guidance and a paragraph describing args and returns. No fluff, well-organized.

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 6 parameters, pagination complexity, many sibling tools, and presence of annotations and output schema, the description covers prerequisites, pagination logic, expected return shape, and alternatives. Fully adequate.

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?

Schema coverage is 100%, baseline 3. Description adds meaning by explaining default limit values (100 vs 25 with detail), the role of pagination parameters, and the return structure (next, hasMore). This enriches the schema alone.

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 it lists nodes in a workspace, specifies it returns one page, and distinguishes from siblings like analyze_workspace_patterns and search_workspace_content. The description is specific about the resource and action.

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 tells when to use (list nodes), when not to use (if complete inventory needed), and provides alternatives (analyze_workspace_patterns, search_workspace_content, get_workspace_node). Also advises to find workspace IDs via list_workspaces.

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