Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Cancel Run

cancel_run
Destructive

Cancel an active pipeline run in Coalesce to stop execution immediately. Requires explicit user confirmation because data may be left inconsistent.

Instructions

Cancel an in-progress Coalesce run. Destructive — the run will be terminated immediately. Canceling a running pipeline mid-execution can leave data in an inconsistent state (partial loads, half-transformed tables). There is no 'undo cancel'.

Args:

  • runID (string, required): Numeric run ID to cancel

  • environmentID (string, required): Environment the run belongs to

  • orgID (string, optional): Organization ID. Falls back to COALESCE_ORG_ID env var or orgID in the active ~/.coa/config profile.

  • confirmed (boolean, optional): Set to true after the user explicitly confirms cancellation

Returns: Confirmation with updated run status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIDNoThe organization ID. Optional if COALESCE_ORG_ID is set, or if `orgID` is present in the active ~/.coa/config profile.
runIDYesThe numeric run ID (integer) of the run to cancel
confirmedNoSet to true after the user explicitly confirms the cancellation.
environmentIDYesThe environment ID the run belongs to

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo
runStatusNo
runCounterNo

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true), the description adds detailed behavioral traits: immediate termination, potential inconsistent state, no undo. 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.

Conciseness5/5

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

The description is well-structured, front-loaded with purpose, and every sentence adds value without redundancy.

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?

For a destructive operation with annotations, complete schema, and output schema, the description covers consequences, parameter details, and return expectation, leaving no gaps.

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%, but the description adds context like runID being numeric, orgID fallback logic, and confirmed param usage, providing meaningful added value.

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 'Cancel an in-progress Coalesce run' with a specific verb and resource, and it distinguishes from sibling tools like retry_run and start_run.

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 warns about data inconsistency and no undo, implying caution, but does not explicitly state when to use vs alternatives like retry_run.

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