Skip to main content
Glama
Datris MCP Server

Datris MCP Server

export_catalog

Back up an entire catalog as a read-only ZIP archive containing taps, pipelines, definitions, scripts, incremental state, and validation schemas; secrets are excluded and listed by name in manifest.

Instructions

Back up a catalog: returns one zip archive of every tap and pipeline in it (definitions, each tap's script and incremental state, referenced validation schemas). Read-only. Secret values are never included; the manifest lists the secret names the catalog needs. Returns manifest (catalog, taps, pipelines, requiredSecrets, warnings) first, then archiveBase64 and sizeBytes. Answer questions about the archive from manifest; pass archiveBase64 unchanged to restore_catalog. Uncataloged cannot be exported.

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": {
      "catalog": "<catalog>"
    },
    "name": "export_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
catalogYesCatalog name to export.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/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 declares read-only behavior, discloses the secret-handling policy (values never included, names listed in manifest), and describes the response shape and ordering (manifest first, then archiveBase64 and sizeBytes). That is exactly the safety and side-effect information an agent needs before calling a backup 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?

Five compact sentences, each doing distinct work: purpose, contents, safety, return shape, and downstream usage. The most decision-relevant facts (what it produces, read-only, no secrets) are front-loaded with no filler.

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, yet the description fully specifies the returned fields and their order, plus the handling instruction for the base64 payload. For a one-parameter read tool, nothing an agent needs to invoke it correctly or interpret its result 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?

Schema description coverage is 100% and the single parameter is already documented as "Catalog name to export." The description implies the catalog must exist and be cataloged ("Uncataloged cannot be exported") but adds no naming format, case sensitivity, or resolution rules beyond the schema. Baseline 3 applies when the schema does the work.

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?

"Back up a catalog" pairs a specific verb with a specific resource, then enumerates exactly what the artifact contains (definitions, tap scripts, incremental state, validation schemas). The restore_catalog handoff makes it trivially distinguishable from the sibling that consumes its output.

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?

The description gives clear operating context: use manifest to answer questions about the archive, pass archiveBase64 unchanged to restore_catalog, and note that uncataloged items cannot be exported. It stops short of an explicit "use this when you need to migrate/clone/back up" framing or a named alternative for inspecting a catalog without exporting it, so it is strong 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