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

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Diagnose Run Failure

diagnose_run_failure
Read-onlyIdempotent

Identify why a Coalesce run failed and get actionable fixes by analyzing each node's error classification and run metadata.

Instructions

Diagnose a failed Coalesce run. Fetches run metadata and per-node results, classifies each failure (SQL error, missing object, permission issue, data type mismatch, timeout, configuration error), and returns actionable fix suggestions.

Use this when a run has failed and the user wants to understand what went wrong and how to fix it. Works best with completed (failed) runs — for in-progress runs, use run_status instead.

Returns: run summary, per-node failure diagnosis with error classification, and prioritized recommendations.

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": {
      "runID": "<runID>"
    },
    "name": "diagnose_run_failure"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIDYesThe numeric run ID (integer, e.g. '401'). Use the runCounter value from start_run or run_status responses — not the UUID from run URLs.

Output Schema

NameRequiredDescriptionDefault
runIDNo
endTimeNo
runTypeNo
summaryNo
failuresNo
warningsNo
runStatusNo
startTimeNo
analyzedAtNo
environmentIDNo
recommendationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and not destructive. Description adds value by explaining it fetches metadata and per-node results, classifies failure types, and returns recommendations. No contradictions.

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?

Three sentences, front-loaded with purpose, then usage, then output. 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?

Description covers input (runID), when to use, what the tool does (failure classification, recommendations), and output summary. Given complexity and existing output schema, description is complete.

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?

Only one parameter runID. Description adds critical context: use runCounter from start_run/run_status, not UUID from URLs. This guidance goes beyond the schema's description, helping the agent avoid common errors.

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 it diagnoses failed Coalesce runs, fetches metadata and per-node results, classifies failures, and returns fix suggestions. Distinguishes from sibling run_status by specifying it's for completed failed runs.

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 says when to use (failed runs) and when not (in-progress runs), names alternative tool run_status. Provides context that it works best with completed failed runs.

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