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

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Run Results

get_run_results
Read-onlyIdempotent

Retrieve execution results for a specific Coalesce run. Obtain per-node status, row counts, and errors using the numeric run ID.

Instructions

Get the execution results of a specific Coalesce run.

Args:

  • runID (string, required): Numeric run ID (integer). Use runCounter, not the UUID.

Returns: Run results including per-node execution status, row counts, and errors.

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": "get_run_results"
  }
}

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
idNo
nameNo
messageNo

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?

Annotations already indicate read-only, idempotent, non-destructive; description adds that it returns per-node status, row counts, errors, enhancing understanding beyond structured fields.

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 plus a concise list; no redundant information, front-loaded purpose.

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?

Simple one-parameter tool with output schema; description sufficiently covers what is needed without over-explaining.

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 covers all parameters, but description clarifies runID is numeric and advises using runCounter over UUID, adding practical 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?

Clearly states it gets execution results of a specific run, distinguishing from siblings like get_run (run metadata) and get_run_details (run details).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for retrieving run results, but lacks explicit guidance on when to use this vs. alternatives like get_run or get_run_details.

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