Skip to main content
Glama
Datris MCP Server

Datris MCP Server

restore_tap_version

Rolls a tap back or forward to a specified definition version by appending it as a new latest version, preserving history. Use when an operator explicitly requests restoring a specific tap version.

Instructions

Roll a tap back (or forward) to a prior definition version. This is APPEND-ONLY and SIDE-EFFECTING: it reads snapshot version and writes it as a NEW latest version (config + that version's script), preserving the full history — nothing is overwritten or lost. 'Rolling forward' is the same call with a higher version number. Only call this when the operator has explicitly asked to restore/roll back this specific tap to a specific version. It does NOT run the tap — after restoring, report the new version and stop; do not chain into run_tap unless separately and explicitly asked. If this Datris instance's agent policy requires a person to approve this action, the call does NOT perform it: it returns status pending_approval with an approvalId. Tell the user it is waiting for approval in Datris, then poll get_approval with that id (pause with wait_seconds between polls) — do not re-issue the action.

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": "restore_tap_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap
reasonNoOptional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it.
versionYesVersion to restore (becomes a new latest version)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does well on semantics: append-only, side-effecting, full history preserved, nothing overwritten. However, it omits the success-shape detail (what the return payload looks like after a successful restore, e.g. version identifiers) and any mention of failure modes such as a nonexistent or out-of-range version number.

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?

Front-loaded with the action and its type, then constraints, then the approval branch — a sensible order with no filler. Some of the anti-chaining and polling instructions are stated at length and could be tightened without losing meaning.

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?

Covers the full operational picture for a side-effecting tool with no annotations and no output schema: immutability guarantee, approval branch with status and approvalId, the follow-up tool and its wait pattern, and an instruction not to over-chain. Little an agent needs to call this correctly is missing.

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 is 3, but the description adds real meaning to `version` by explaining that a higher number performs a roll-forward rather than a rollback. The `reason` audit/approval meaning is already in the schema, so that portion is redundant rather than additive.

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 ('Roll a tap back (or forward) to a prior definition version') and immediately clarifies the key ambiguity that roll-forward is the same call. An agent can distinguish this from get_tap_version, diff_tap_versions, and restore_pipeline_version/restore_script_version without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit gating condition ('Only call this when the operator has explicitly asked to restore/roll back this specific tap to a specific version') and an explicit exclusion ('It does NOT run the tap... do not chain into run_tap unless separately and explicitly asked'). It also routes the agent to the correct follow-up path (get_approval, wait_seconds) when approval is pending.

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