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

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Retry Run

retry_run

Retry a failed Coalesce run by providing the run ID. Supports optional parameters and forced retry even if deploy failed.

Instructions

Retry a failed Coalesce run. Requires Snowflake auth via environment variables (Key Pair or PAT).

Args:

  • runDetails.runID (string, required): The run ID to retry

  • runDetails.forceIgnoreWorkspaceStatus (boolean, optional): Force retry even if deploy failed

  • parameters (object, optional): Runtime parameters

Returns: { runCounter, runStatus, message }

Prefer retry_and_wait when you need the final outcome in a single call.

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": {
      "runDetails": "<runDetails>"
    },
    "name": "retry_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersNoArbitrary key-value parameters to pass to the rerun
runDetailsYes

Output Schema

NameRequiredDescriptionDefault
messageNo
runStatusNo
runCounterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4.3/5.0
Behavior4/5

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

Discloses that forceIgnoreWorkspaceStatus forces retry even if deploy failed, and notes caution. Requires Snowflake auth. Annotations already indicate non-readonly and non-idempotent; description adds context without 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?

Structured with Args/Returns, front-loaded purpose sentence. No fluff, but the Args section could be more concise by referencing schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers auth requirement, parameter caution, return shape, and points to sibling tool. Reasonably complete given has output schema and good annotations.

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 covers both parameters well (runID pattern, forceIgnoreWorkspaceStatus caution). Description adds minimal extra meaning beyond schema, so 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?

Clearly states 'Retry a failed Coalesce run' with specific verb (retry) and resource (run). Differentiates from sibling retry_and_wait by noting it returns final outcome.

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 recommends retry_and_wait when final outcome is needed, and mentions Snowflake auth prerequisites. Provides clear guidance on when to use alternatives.

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