Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_tap_version

View a historical snapshot of a tap’s full configuration and pinned Python script at a specific version without changing the live tap; use version numbers from list_tap_versions.

Instructions

View one historical snapshot of a tap's definition: the full config and the pinned Python script as they were at that version. Read-only; does not change the live tap. Get version numbers from list_tap_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_tap_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap
versionYesVersion number to view

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description must carry the safety profile and it does: "Read-only; does not change the live tap" tells the agent this is a non-mutating fetch. It also discloses what the payload contains (config and pinned script at that version), though it says nothing about behavior for a nonexistent version or the size of the returned snapshot.

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?

Two sentences, front-loaded with the core action and scope, followed by a pointer to the sibling that supplies the version number. No redundant restatement of the tool name and no filler.

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 two-parameter read with no output schema, the description usefully previews the return contents and confirms non-mutating behavior. The remaining gap is error/edge behavior (unknown version, very large configs), which is minor for this complexity level.

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 the baseline is 3, but the description adds real meaning by stating that version identifiers should be sourced from `list_tap_versions` rather than guessed. That provenance hint is the kind of guidance the schema cannot provide.

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 historical snapshot of a tap's definition") and immediately qualifies scope: a single version, not the live tap. It names the exact contents (full config plus pinned Python script), which separates it cleanly from get_tap and list_tap_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?

Explicitly routes the agent to `list_tap_versions` to obtain version numbers, and the phrase "does not change the live tap" implies the contrast with restore_tap_version. It stops short of naming restore_tap_version or get_tap directly as alternatives, so the routing is clear but not exhaustive.

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