Skip to main content
Glama
dolphin-mcp-pilot

dolphin-mcp-pilot

ds_list_workflow_versions

Lists saved versions of a workflow definition to review version numbers, descriptions, and timestamps before selecting one for rollback.

Instructions

List saved versions of a workflow definition (read-only).

Each save of the workflow creates a version. Use the returned version number with ds_rollback_workflow_version.

Args: project_name: Project name workflow_code: Workflow (process-definition) code from ds_list_workflows page_size: Maximum number of versions to return (first page, default 20)

Returns: [{"version": int, "description": str, "createTime": str, "updateTime": str}, ...]

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": {
      "project_name": "<project_name>",
      "workflow_code": "<workflow_code>"
    },
    "name": "ds_list_workflow_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_sizeNo
project_nameYes
workflow_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description still discloses that the tool is read-only, that versions accrue on every save, and that only the first page (default 20) is returned, so the agent knows results can be truncated. It omits ordering (newest vs oldest first) and any permission requirements, which are the remaining behavioral unknowns.

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?

Purpose is front-loaded in the first sentence, followed by the Args/Returns blocks that make scanning easy. The 'Returns' block duplicates runtime information well, though the Args lines for project_name add little beyond the schema titles.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with no annotations and no output schema, the description covers the return record shape, the meaning of a version, and the paging cap. The gap is what happens beyond the first page and the ordering of versions, which an agent would need to reason about rollback selection.

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 0%, so the description must carry the burden and it partially does: workflow_code is given provenance from ds_list_workflows and page_size is explained as a first-page cap with default 20. However, project_name is merely restated as 'Project name' with no format or source guidance, so one of three parameters stays opaque.

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 ('List saved versions of a workflow definition') plus scope ('read-only') and immediately ties the result to a concrete downstream use. An agent can distinguish this from ds_rollback_workflow_version and ds_list_workflows without opening any 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?

Explains the domain model ('each save of the workflow creates a version') and names the follow-up tool ds_rollback_workflow_version, which tells the agent why to call this. It does not state explicit exclusions or when-not-to-use conditions, keeping it short of a 5.

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