Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_tap_versions

Retrieves a tap's change history, newest first, with version, createdAt, createdBy, and changeNote. Use it to see what changed and when; an empty result means no change snapshots exist yet.

Instructions

List the change HISTORY of a tap's definition, newest first. Each entry has version, createdAt, createdBy, and changeNote. The platform snapshots a tap's config + script every time it is created or updated. Read-only. IMPORTANT: an EMPTY result does NOT mean the tap has no version — it means the tap has not been edited since versioning was enabled, so no change snapshots exist yet. The tap's CURRENT version number is the version field on the tap itself (from list_taps or get_tap), which is at least 1 for every tap. Use this tool for 'what changed and when'; use list_taps/get_tap for 'what version is it on now'. See also get_tap_version, diff_tap_versions, restore_tap_version.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares read-only behavior, explains the snapshot mechanism (config + script captured on every create/update), and disambiguates the empty-result case. It stops short of covering pagination, result-size limits, or whether history is retained indefinitely, which are the remaining behavioral unknowns for a history-listing endpoint.

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?

Front-loaded with purpose and ordering, then the return fields, then the critical empty-result caveat, then routing guidance. Every sentence carries operational value; the 'at least 1 for every tap' clause exists specifically to prevent a false negative inference.

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?

No output schema exists, so the description compensates by naming the entry fields (version, createdAt, createdBy, changeNote) and by clarifying the relationship between history entries and the tap's current version number. For a single-parameter read tool, nothing an agent needs to call and interpret it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter and schema coverage is 100%, so the schema already fully documents `name`. The description adds context that the name identifies the tap whose definition history is returned, but nothing about name format, scoping, or error behavior when the tap doesn't exist — baseline 3 is appropriate.

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 ('List the change HISTORY of a tap's definition') plus ordering ('newest first'), and immediately differentiates itself from list_taps/get_tap, which report the current version rather than history. An agent can distinguish it from the versioning siblings without opening a 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?

Explicitly assigns use cases: 'what changed and when' for this tool versus 'what version is it on now' for list_taps/get_tap, and points to get_tap_version, diff_tap_versions, and restore_tap_version. It also warns that an empty result does not mean the tap lacks a version, which is exactly the misread an agent would otherwise make.

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