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

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

Output 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.5/5.0

Behavior5/5

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

Annotations already declare a safe read, but the description adds what an agent genuinely cannot infer: output is decoded as a string, output_truncated signals sampling, and stored output is severely truncated for endpoint-serve runs. That truncation caveat materially changes how an agent should interpret results.

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 tight sentences: what it returns first, then the truncation semantics and the workaround. No filler, no repetition of the title, and the most decision-relevant caveat is easy to find.

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 exists, yet the description still flags the non-obvious truncation behavior that the schema cannot convey. Combined with the safe-read annotations and a single documented id parameter, nothing needed to call or interpret this tool is missing.

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?

With one parameter at 100% schema coverage, the schema already explains run_id as the id returned by run_workflow. The description repeats 'by run id' without adding format, source, or validation detail beyond what the schema gives, so 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?

The description names a specific verb and resource (get the stored record of a past workflow run) plus the key selector (by run id) and the payload it returns (status, content_type, output). It clearly separates itself from run_workflow (triggers) and from list_runs (enumerates) simply by describing stored-record retrieval.

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 a concrete rule: runs from a LIVE ENDPOINT SERVE are truncated, so re-run or preview the endpoint to see a full render, whereas runs you triggered via run_workflow or preview are stored in full. That tells the agent when this tool's output is sufficient and when to route elsewhere. It only stops short of naming list_runs as the source of run ids.

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?