Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Get Upstream Nodes

get_upstream_nodes
Read-onlyIdempotent

Walk the entire upstream lineage of a node to retrieve all ancestor nodes with their depth, enabling dependency analysis without depth restrictions.

Instructions

Walk the full upstream dependency graph for a node and return every ancestor with its depth level.

Args: workspaceID: Workspace to query nodeID: Starting node whose upstream lineage to trace

Returns: Array of ancestor nodes with nodeID, nodeName, nodeType, and depth (1 = direct parent). Traverses the entire graph with no depth limit. Nodes are deduplicated.

Requires a lineage cache — will fetch all workspace nodes with detail=true on first call (may take a moment for large workspaces). Subsequent calls use the cached graph (default TTL: 30 min).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIDYesNode ID to trace upstream from
workspaceIDYesWorkspace ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIDNo
nodeNameNo
nodeTypeNo
ancestorsNo
dependentsNo
totalAncestorsNo
totalDependentsNo
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds deduplication and cache mechanism without contradicting 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?

Concise, front-loaded, every sentence adds value. No wasted words.

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?

Covers return format, cache behavior, and with output schema present, description is complete for this 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 coverage is 100%, so description adds little beyond listing parameters in Args. Baseline 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?

Description clearly states the tool walks the full upstream dependency graph returning ancestors with depth. Distinguishes from siblings like get_downstream_nodes and analyze_impact.

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?

Specifies graph traversal has no depth limit, and mentions cache behavior. Does not explicitly provide when-not-to-use or alternatives, but context is clear.

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