Skip to main content
Glama
Datris MCP Server

Datris MCP Server

diff_tap_versions

Compare two versions of a tap definition to identify config and script changes against a baseline, returning field-by-field and line-level diffs.

Instructions

Compare two versions of a tap's definition. Returns a server-computed field-by-field config diff and a line-level diff of the script. Read-only. version is the newer/selected snapshot; against is the baseline to compare it to.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap
againstYesBaseline version to compare against
versionYesSelected version

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 safety profile, and it does state 'Read-only', which is the single most important behavioral fact. It also discloses the shape of the result (server-computed field-by-field config diff plus line-level script diff). It says nothing about failure behavior, permissions, or size limits on the diff, so gaps remain 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with purpose, then return shape, then safety, then the parameter-role clarification. No filler, no restatement of the tool name, and each sentence adds a distinct fact.

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?

There is no output schema, so the description correctly spends a sentence characterizing the returned diff, and it covers read-only safety and parameter direction. For a three-parameter comparison tool this is nearly complete; only error conditions and any constraints on version existence or auth are unaddressed.

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 baseline would be 3, but the description adds genuine meaning beyond the schema by disambiguating which parameter is the newer snapshot and which is the baseline, which determines diff direction. The schema alone labels them only 'Selected version' and 'Baseline version to compare against', so the explicit ordering clarification is useful.

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 gives a specific verb and resource ('Compare two versions of a tap's definition') and even enumerates the two outputs, a field-by-field config diff and a line-level script diff. It implicitly separates itself from diff_pipeline_versions and diff_script_versions by naming the tap resource, but never explicitly contrasts with them, so sibling differentiation is left partly to inference.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for comparing two tap snapshots, and the last sentence clarifies which role each version plays. There is no statement of when not to use it (e.g. versus get_tap_version or diff_script_versions) and no prerequisites such as the need for both versions to exist.

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