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 with its full builder definition, step parameter values, and value-light projection. Use to inspect or compare past workflow configurations.

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, so the safe read behavior is covered. The description adds useful behavioral context by specifying exactly what the response includes—the full builder definition with step parameter values and the value-light projection—which goes beyond the structured 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 concise sentences with no filler. The first states the core behavior and returned content, and the second gives routing guidance. Every sentence earns its place.

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?

For a read-only, two-parameter tool with complete schema descriptions and an output schema present, the description provides all needed calling context plus explicit guidance on when not to use it. Nothing critical 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 description coverage is 100%, so the input schema fully documents both workflow_id and version. The description does not add new parameter-level detail beyond the schema, which matches the baseline expectation.

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 uses a specific verb and resource: 'Get one exact workflow version' and explains what is included ('full builder definition with step parameter values and its value-light projection'). It also distinguishes itself from get_workflow by referencing 'current_version', so an agent can disambiguate the sibling tools without inspecting schemas.

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?

The description explicitly states when to use this tool versus the alternative: 'Use current_version from get_workflow unless you intentionally need an older version.' This gives a clear condition and names the alternative tool directly.

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