Skip to main content
Glama
Datris MCP Server

Datris MCP Server

diff_script_versions

Compare two versions of a pipeline's AI data-quality rule or transformation script and get a line-by-line diff showing added, deleted, and context lines for review.

Instructions

Compare two versions of a pipeline's AI data-quality rule or AI transformation script. Returns a server-computed line diff: script.lines entries typed ctx, add or del. Read-only. version is the newer/selected version; against is the baseline.

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>",
      "against": "<against>"
    },
    "name": "diff_script_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich script: the AI data-quality rule or the AI transformation
nameYesName of the pipeline
againstYesBaseline version to compare against
versionYesSelected version

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden, and it does disclose two useful traits: the operation is read-only and the result is a server-computed line diff whose `script.lines` entries are typed `ctx`, `add` or `del`. It says nothing about error behavior (unknown name, missing version), whether `version` may equal `against`, or any ordering guarantees, which is a real gap 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?

Roughly three short sentences, front-loaded with the purpose before the return shape and parameter direction; nothing is padded. The closing version/against sentence partially restates the schema labels, which costs it a point but it also adds the "newer" qualifier that makes it worthwhile.

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 four-required-parameter, no-output-schema tool, the description covers purpose, output structure, read-only nature, and parameter direction - sufficient for an agent to select and invoke it correctly. Remaining omissions (auth, error cases) are secondary for a pure read/compare operation.

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 description coverage is 100%, so a baseline of 3 applies, but the description adds a directional detail the schema lacks: `version` is specifically the newer/selected version and `against` is the baseline. That resolves ambiguity about diff direction (which side is add vs del) beyond the schema's terse "Selected version" label.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: "Compare two versions of a pipeline's AI data-quality rule or AI transformation script." The scope (scripts, keyed by the `kind` enum) implicitly separates it from diff_pipeline_versions and diff_tap_versions, but it never names or routes to those siblings explicitly, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this instead of get_script_version or list_script_versions, nor any prerequisite such as needing both versions to exist or being authorized on the pipeline. The only usage-adjacent content is the read-only note and a direction hint for the two version parameters, which is descriptive rather than prescriptive.

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