Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_pipeline_versions

Lists a pipeline's change history, newest first, showing each version number, timestamp, author, and change note. Use it to see what changed and when.

Instructions

List the change HISTORY of a pipeline's definition, newest first. Each entry has version, createdAt, createdBy, and changeNote. The platform snapshots a pipeline's full config every time it is created or updated. Read-only. IMPORTANT: an EMPTY result does NOT mean the pipeline has no version — it means it has not been edited since versioning was enabled. The CURRENT version number is the version field on the pipeline itself (from list_pipelines or get_pipeline), at least 1 for every pipeline. Use this tool for 'what changed and when'; use list_pipelines/get_pipeline for 'what version is it on now'. See also get_pipeline_version, diff_pipeline_versions, restore_pipeline_version.

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": {
      "name": "<name>"
    },
    "name": "list_pipeline_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the pipeline

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the load and does so well: it declares read-only status, explains snapshot semantics (full config captured on every create/update), and pre-empts the dangerous misreading of an empty result. It stops short of describing pagination or result-size limits for long histories.

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 action, then caveats, then alternatives — a good ordering. Dense but almost every sentence carries distinct information; the closing 'See also' list adds names without routing guidance.

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

Completeness3/5

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

Strong on semantics, but with no output schema and no annotations, an agent still lacks return-type detail (e.g. whether version is a number or string, whether entries can be paginated/truncated) and confirmation of the auth/scope requirements for reading a pipeline's history.

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?

Only one parameter and schema coverage is 100%, so the schema already defines 'name'; the description adds no matching rules, case sensitivity, or error behavior for an unknown name. The field list it provides describes the return shape rather than parameter meaning.

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 the change HISTORY of a pipeline's definition') plus ordering ('newest first') and the exact returned fields, so it is immediately distinguishable from get_pipeline/list_pipelines.

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 divides work with siblings: 'Use this tool for what changed and when; use list_pipelines/get_pipeline for what version is it on now,' and points to get_pipeline_version, diff_pipeline_versions, and restore_pipeline_version by name.

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

Deploy Server

Other Tools