Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Update Workspace Subgraph

update_workspace_subgraph

Update a subgraph's name and member nodes by replacing the entire steps array. Resolve subgraph by ID or name using local cache or repo path.

Instructions

Update a subgraph's name and member nodes. Replaces the entire steps array. Pass either subgraphID (fastest) or subgraphName — if only the name is given, the ID is resolved from (1) the local UUID cache, (2) {repoPath}/subgraphs/*.yml. The public Coalesce API has no subgraph list endpoint, so a subgraph created outside this MCP session cannot be resolved by name without a repo checkout.

Args:

  • workspaceID (string, required): The workspace ID

  • subgraphID (string, optional): The subgraph ID. Preferred when known.

  • subgraphName (string, optional): The subgraph name. Used to resolve the ID when subgraphID is absent.

  • repoPath (string, optional): Coalesce repo path for subgraph YAML lookup.

  • name (string, required): Updated name

  • steps (string[], required): Updated node IDs

Returns: { subgraphID, subgraph, resolvedFrom } where resolvedFrom is "input" | "cache" | "repo".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUpdated name for the subgraph
stepsYesUpdated array of node IDs to include in the subgraph
repoPathNoOptional Coalesce repo path for subgraph YAML lookup. Falls back to COALESCE_REPO_PATH or the coa profile.
subgraphIDNoThe subgraph ID. Preferred when known — fastest path.
workspaceIDYesThe workspace ID
subgraphNameNoThe subgraph name. Used to resolve the ID from the local cache or repo subgraphs/ folder when subgraphID is absent (the Coalesce API has no subgraph list endpoint).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
messageNo
Behavior5/5

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

Discloses that the steps array is entirely replaced (destructive to previous steps) and explains the ID resolution mechanism. This adds valuable context beyond annotations, which only hint at non-readonly, non-idempotent, non-destructive behavior. No contradiction.

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 bullet points for arguments and returns, front-loading the main action. It is thorough but could be slightly more concise; however, the detail is warranted given the tool's complexity.

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 prerequisites (ID resolution), side effects (replaces steps), return values, and edge cases (subgraph created outside session). With an output schema implied and the description providing return field details, it is complete for a complex tool.

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?

Schema coverage is 100%, but the description adds context about resolution order, fallback to environment variables, and the return object structure. This significantly aids the agent in understanding parameter relationships beyond the schema.

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 updates a subgraph's name and member nodes, replaces the entire steps array. The verb 'update' and resource 'subgraph' are specific, distinguishing it from siblings like create_workspace_subgraph and delete_workspace_subgraph.

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?

Provides explicit guidance on using subgraphID vs subgraphName, explains the resolution order (fastest path), and mentions the API limitation. However, it does not explicitly state when not to use this tool or list alternative tools for similar tasks.

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