Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get workflow version

get_workflow_version

Read-only

Retrieve a specific workflow version by ID and version number to inspect its full builder definition, step parameter values, and value-light projection.

Instructions

Get one exact workflow version, including its full builder definition with step parameter values and its value-light projection. Use current_version from get_workflow unless you intentionally need an older version.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`version`	Yes	The positive version number to retrieve.
`workflow_id`	Yes	The workflow's UUID.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`author`	Yes
`version`	Yes
`created_at`	Yes
`definition`	No	Arbitrary JSON owned by the producing engine.
`projection`	No	Arbitrary JSON owned by the producing engine.
`chat_run_id`	Yes
`workflow_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.16.0Sep 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "author": {
+      "type": "string"
+    },
+    "chat_run_id": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "definition": {
+      "description": "Arbitrary JSON owned by the producing engine."
+    },
+    "id": {
+      "type": "string"
+    },
+    "projection": {
+      "description": "Arbitrary JSON owned by the producing engine."
+    },
+    "version": {
+      "maximum": 2147483647,
+      "minimum": -2147483648,
+      "type": "integer"
+    },
+    "workflow_id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "workflow_id",
+    "version",
+    "author",
+    "chat_run_id",
+    "created_at"
+  ],
+  "type": "object"
+}

Addedv0.9.0Aug 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the returned content shape ('full builder definition with step parameter values and its value-light projection'), which goes beyond the structured fields, though it says nothing about pagination or payload size.

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 tight sentences, front-loaded with the resource and payload, followed by the routing guidance. No filler.

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, so return values need not be enumerated; the description nonetheless characterizes the payload. Combined with 100% parameter coverage and existing annotations, nothing an agent needs to invoke this tool correctly 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?

Schema coverage is 100% and both parameters are fully documented in the schema (positive version number, workflow UUID). The description adds no syntax or format detail beyond what the schema already provides, 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 ('Get') and resource ('one exact workflow version') and details what the payload contains (builder definition with step parameter values and value-light projection). This clearly distinguishes it from the sibling get_workflow, which returns the current workflow rather than a pinned version.

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 routes the agent: 'Use current_version from get_workflow unless you intentionally need an older version.' This names the alternative tool and the exact condition (fetching a historical version) that selects this one.

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