Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_script_versions

Lists the version history of a pipeline's AI data-quality or transformation script, newest first, with metadata on each change and which version is live.

Instructions

List the version HISTORY of the script the pipeline runs for its AI data-quality rule or AI transformation (kind), newest first. Each entry has version, createdAt, createdBy, changeNote, origin (save, regenerate, run, restore-version, restore, repository), model, commitSha (repository-backed scripts), fingerprintMatchesCurrent (written for the pipeline's current instruction and source schema) and isLive (the script runs now use). Every change to the script is kept; the pipeline's definition version does not change when its script does. Read-only. See also get_script_version, diff_script_versions, restore_script_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>",
      "kind": "<kind>"
    },
    "name": "list_script_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich script: the AI data-quality rule or the AI transformation
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 are supplied, so the description must carry the full behavioral burden, and it does well: it declares read-only status, newest-first ordering, retention semantics ("Every change to the script is kept"), and the important invariant that the pipeline definition version does not change when its script does. It does not cover pagination or result-size limits, which keeps it from a 5 for an unannotated tool.

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 and ordering are front-loaded in the first clause, and the see-also routing closes it cleanly. The middle sentence is a dense enumeration of return fields, which is long but justified because no output schema exists to carry that information.

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?

With no output schema and no annotations, the description supplies precisely what is missing: the meaning of every returned field, the origin enum values, the fingerprintMatchesCurrent and isLive semantics, and the read-only/ordering behavior. For a two-parameter listing tool, nothing an agent needs to call it correctly is absent.

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 both `name` and `kind` are already documented, including the enum values. The description's phrasing ("the script the pipeline runs for its AI data-quality rule or AI transformation") adds only framing context about what `kind` selects, not new semantics for either parameter, 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 and resource ("List the version HISTORY of the script the pipeline runs") and scopes it to the two `kind` variants, with ordering ("newest first") included. It clearly differentiates itself from `get_script_version`, `diff_script_versions`, and `restore_script_version` via the See-also routing sentence.

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?

The description gives clear context for when this tool applies (enumerating version history for a pipeline's AI rule or transformation) and names the three sibling tools that cover the adjacent operations. It stops short of explicit conditionals such as "use this instead of get_script_version when..." or when-not guidance, so it lands just below the top band.

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