Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_pipeline_version

View a historical snapshot of a pipeline's full configuration at a specific version without altering the live pipeline; get version numbers from list_pipeline_versions.

Instructions

View one historical snapshot of a pipeline's definition: the full config as it was at that version. Read-only; does not change the live pipeline. Get version numbers from list_pipeline_versions.

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>",
      "version": "<version>"
    },
    "name": "get_pipeline_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the pipeline
versionYesVersion number to view

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the whole behavioral burden; it does disclose the most important trait (read-only, does not alter the live pipeline) and that it returns the full historical config. It doesn't say what happens for an unknown or out-of-range version, nor whether any permission or retention limits apply to historical snapshots.

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 short clauses, front-loaded with the return content before the behavioral note and the pointer to the version source. Nothing is redundant and nothing is buried.

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 trivial two-parameter read with no output schema, the description covers purpose, side-effect safety, return content ('the full config as it was at that version'), and how to obtain the version number. Only error/edge-case behavior for invalid versions is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented and baseline is 3. The description earns the bump by explaining where `version` values come from (`list_pipeline_versions`) and by characterizing `name` implicitly as identifying the pipeline whose history is being read.

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?

Names a specific verb (view), a precise resource (one historical snapshot of a pipeline's definition), and explicitly scopes it to the config 'as it was at that version,' which separates it from the live-pipeline reader get_pipeline without needing the sibling's schema opened.

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?

Gives concrete entry-point guidance ('Get version numbers from `list_pipeline_versions`') and clarifies the read-only, non-mutating context. It stops short of explicitly excluding alternatives such as get_pipeline for current state or diff_pipeline_versions for comparison, so an agent must infer those boundaries.

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