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

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Pipeline Workshop Close

pipeline_workshop_close
Idempotent

Close a pipeline workshop session and clean up the session state to finalize the workspace.

Instructions

Close a pipeline workshop session and clean up the session state. If there are uncreated nodes in the plan, use build_pipeline_from_intent or plan_pipeline to create them before closing.

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": {
      "sessionID": "<sessionID>"
    },
    "name": "pipeline_workshop_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIDYesThe workshop session ID to close

Output Schema

NameRequiredDescriptionDefault
errorNo
closedNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false; the description adds behavioral context about cleaning session state and handling uncreated nodes, which is consistent 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?

Two sentences with no fluff: first sentence states purpose, second provides conditional usage guidance. Front-loaded and efficient.

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 the tool's simplicity (close operation with one parameter) and the existence of an output schema, the description adequately covers purpose, usage conditions, and prerequisite actions, making it complete.

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% for the single parameter sessionID, so the description adds no additional semantic detail beyond what the schema already provides, meeting the baseline for high 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?

The description clearly states the verb (close) and resource (pipeline workshop session), and it distinguishes itself from sibling tools like pipeline_workshop_open and pipeline_workshop_instruct by specifying cleanup of session state.

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 provides when-not-to-use guidance by mentioning uncreated nodes and suggests two alternative tools (build_pipeline_from_intent, plan_pipeline) to handle that case before closing.

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