Tessryx

Get workflow run

get_workflow_run

Read-onlyIdempotent

Get the stored record of a past workflow run by run id: status, content_type, and the output (decoded as a string; output_truncated is true when the stored output was sampled down). Runs from a LIVE ENDPOINT SERVE keep only the first few KB of the page — re-run or preview the endpoint to see a whole render. Runs you triggered (run_workflow, preview) store their output in full.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`run_id`	Yes	the run id returned by run_workflow

Output Schema

TableJSON Schema

Name	Required	Description
`chain`	No	present only for a run that is part of a chain: its place in it and whether the chain continues after it
`error`	No
`output`	No
`run_id`	Yes
`status`	Yes
`message`	No
`workflow_id`	Yes
`content_type`	Yes
`output_truncated`	No
`workflow_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedOutput schema / properties / chain

Added value: +{
+  "additionalProperties": false,
+  "description": "present only for a run that is part of a chain: its place in it and whether the chain continues after it",
+  "properties": {
+    "chain_id": {
+      "description": "the chain's id: the run_id of its first run",
+      "type": "string"
+    },
+    "continues": {
+      "description": "true if another run of the chain was queued after this one; false on the last run, when the chain has finished",
+      "type": "boolean"
+    },
+    "link_index": {
+      "description": "this run's place in the chain, 0 for the first",
+      "maximum": 2147483647,
+      "minimum": -2147483648,
+      "type": "integer"
+    },
+    "origin": {
+      "description": "what started the chain when it was not a schedule: mcp, schedule_manual",
+      "type": "string"
+    }
+  },
+  "required": [
+    "chain_id",
+    "link_index",
+    "continues"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description adds value by disclosing output semantics: output is decoded as a string, output_truncated flags sampled-down data, and truncation specifically affects LIVE ENDPOINT SERVE runs. This goes well beyond what the annotations convey.

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?

Front-loaded with the core purpose and then layered with output/truncation caveats; each sentence carries information (fields, decoding, truncation trigger, full-storage cases). It is a touch dense but no sentence is wasted.

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?

An output schema and annotations are present, so return-value and safety disclosure are already covered; the description usefully supplements with truncation and output-decoding behavior. An agent has everything needed to call this read-only fetch correctly.

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?

There is a single parameter with 100% schema coverage, and the schema already explains run_id as 'the run id returned by run_workflow' with a required constraint. The description only echoes 'by run id' without adding format or provenance detail, so the baseline 3 applies.

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?

States a specific verb and resource ('Get the stored record of a past workflow run') and enumerates the payload (status, content_type, output), which effectively separates it from get_workflow (definition), list_runs, and get_workflow_run_traces. An agent knows exactly what comes back without opening the schema.

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?

It gives clear runtime context for choosing this tool's output: live-endpoint serves keep only the first few KB, while runs from run_workflow/preview are stored in full, and it points to re-running or previewing when a full render is needed. It stops short of explicitly contrasting with the closest sibling (get_workflow_run_traces) or list_runs, so it is strong but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tessryx tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?