Skip to main content
Glama
Datris MCP Server

Datris MCP Server

restore_pipeline_version

Restore a pipeline to a prior definition version by writing that snapshot as a new latest version, keeping full history. Use when an operator asks to roll a pipeline back or forward to a specific version.

Instructions

Roll a pipeline back (or forward) to a prior definition version. APPEND-ONLY and SIDE-EFFECTING: reads snapshot version and writes it as a NEW latest version, preserving full history. '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 pipeline to a specific version. Report the new version and stop. 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_pipeline_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the pipeline
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.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses that the operation is append-only and side-effecting, that it writes a new latest version rather than mutating history, and that under an approval policy the call does not execute but returns status 'pending_approval' with an approvalId. That is exactly the non-obvious runtime behavior an agent needs before invoking a mutation.

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?

The description is front-loaded with the core action and the APPEND-ONLY/SIDE-EFFECTING warning, then proceeds in a logical order to the gating condition and the approval path. It is longer than average but nearly every sentence adds operative information; only the 'report the new version and stop' instruction is slightly redundant with the approval guidance.

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?

There is no output schema, so the description supplies the return semantics itself (new version, or status 'pending_approval' with an approvalId), plus the required follow-up procedure. For a side-effecting, approval-gated restore tool this covers everything an agent needs to call it and handle the response correctly.

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 genuine meaning beyond the schema by explaining that `version` is read as a snapshot and written as a NEW latest version, and that 'rolling forward' is the same call with a higher version number. It does not mention the optional `reason` parameter, so it stops short of full coverage.

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?

The description gives a specific verb and resource ('Roll a pipeline back (or forward) to a prior definition version') and immediately clarifies the append-only semantics, which distinguishes it from siblings like get_pipeline_version, list_pipeline_versions, and diff_pipeline_versions. An agent can tell exactly what this call does without opening the 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?

It states an explicit gate ('Only call this when the operator has explicitly asked to restore/roll back this specific pipeline to a specific version'), gives a post-call instruction ('Report the new version and stop'), and names the follow-up tools and sequence for the approval path (poll get_approval, pause with wait_seconds, do not re-issue). Both when-to-use and the alternative flow are spelled out.

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