Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_script_version

Retrieve a specific version of a pipeline's AI data-quality rule or AI transformation script, including full script text, fingerprint, generatedAt, and contractVersion, for read-only inspection.

Instructions

View one version of a pipeline's AI data-quality rule or AI transformation script: the list fields plus the full script text, fingerprint, generatedAt and contractVersion. Read-only; does not change what the pipeline runs. Get version numbers from list_script_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>",
      "kind": "<kind>",
      "version": "<version>"
    },
    "name": "get_script_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich script: the AI data-quality rule or the AI transformation
nameYesName of the pipeline
versionYesScript version number to view

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does address the key behavioral question: 'Read-only; does not change what the pipeline runs.' It also compensates for the missing output schema by naming the returned fields (script text, fingerprint, generatedAt, contractVersion). It does not mention size/truncation behavior for the potentially large `script` text, which is a real gap for this tool.

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 sentences, front-loaded with the action and the returned payload, followed by the safety statement and the prerequisite. No filler or redundant restatement of the tool name.

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 simple three-parameter read tool with no output schema and no annotations, the description covers purpose, output contents, safety posture, and how to source the version argument. Nothing an agent needs in order to call it correctly is missing, apart from optional notes on large script payloads.

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% with enum values and per-parameter descriptions, so the baseline is 3. The description adds a small amount of meaning beyond the schema by telling the agent where valid `version` values come from (`list_script_versions`) and clarifying the two enum branches in prose.

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 ('View one version of a pipeline's AI data-quality rule or AI transformation script') and immediately enumerates what is returned: list fields, full `script` text, `fingerprint`, `generatedAt`, `contractVersion`. That specificity clearly separates it from sibling readers like `list_script_versions` or `diff_script_versions`.

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 an explicit prerequisite route ('Get version numbers from `list_script_versions`') and states the read-only posture, which implicitly distinguishes it from `restore_script_version`. It stops short of naming an explicit when-not or naming restore as the alternative for writes, so it is clear context rather than full routing guidance.

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