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

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Run Details

get_run_details
Read-onlyIdempotent

Retrieve run metadata and execution results in a single API request. Input the numeric run ID to get combined run details and results.

Instructions

Get run metadata and execution results in a single call. Combines get_run and get_run_results.

Args:

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

Returns: { run: RunObject, results: ResultsObject, resultsError?: ErrorObject }

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_details"
  }
}

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
runNo
resultsNo
resultsErrorNo

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 declare readOnlyHint, idempotentHint, destructiveHint false. The description adds context that it combines two calls into one and returns a combined object with possible error, which is useful 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 clear sentences plus structured arg/return spec. No unnecessary words, front-loaded with 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?

Given the simple single-parameter tool, output schema exists, and description covers purpose, parameter guidance, and return structure. 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%, providing baseline. Description adds clarifying guidance: 'Numeric run ID (integer). Use runCounter, not the UUID.' This provides additional semantic value beyond schema.

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 tool retrieves run metadata and execution results, combining two existing calls. It specifies the resource (run) and action (get), and distinguishes from siblings get_run and get_run_results.

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 explicitly indicates this tool combines get_run and get_run_results, implying when to use instead of separate calls. It also instructs to use runCounter rather than UUID. However, it does not provide explicit when-not-to-use scenarios.

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