Skip to main content
Glama
Datris MCP Server

Datris MCP Server

enable_catalog_ordered

Starts a server-side job that enables a catalog's taps level by level in their defined enable order, testing and running each tap before moving on. Returns a job id to track progress.

Instructions

Start one server-side job that enables a catalog's taps in their enable order (see catalog_enable_order): level by level, each tap is tested if it has no passing test, enabled, given one real run, and the job waits until that run's data has landed before moving on. A tap whose source did not land data is skipped with the reason; every tap's outcome is reported. Call this ONLY when the user has asked to enable the catalog's taps. It returns at once with the job id and the plan; follow progress with catalog_enable_order (its job block), pausing with wait_seconds between polls, until job.active is false, then report each tap's phase and reason. While the job runs, do not call run_tap, test_tap or update_tap on that catalog's taps: the job is already running them. Refused while another enable job for the catalog is running, or when its taps have a dependency cycle (the cycles are returned). Cancelling is done by the user in Datris. 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": {
      "catalog": "<catalog>"
    },
    "name": "enable_catalog_ordered"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it.
catalogYesCatalog name.

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, the description carries the full burden and does: it discloses asynchronous return (job id + plan), concurrency exclusions ('do not call run_tap, test_tap or update_tap on that catalog's taps'), refusal conditions (another running job, dependency cycles returning `cycles`), cancellation ownership (user in Datris), and the pending_approval/approvalId flow.

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?

Well front-loaded with the action and return shape first, then operational rules. It is dense (roughly eight clauses in one paragraph) and would scan faster as a short bullet list, but almost every sentence carries necessary operational information.

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 asynchronous job trigger this covers purpose, return contract, polling, refusals, and approval handling. The one gap is that the shape of the `job` block and per-tap outcome fields are described only by name, with no output schema to fall back on.

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 coverage is 100%, so both `catalog` and `reason` are already documented in the schema, including the audit-log/approval-display note for `reason`. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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 opening sentence gives a concrete verb and resource ('Start one server-side job that enables a catalog's taps in their enable order') and immediately points to catalog_enable_order for the ordering definition, so it is distinguishable from siblings like run_tap or test_tap.

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 restricts invocation ('Call this ONLY when the user has asked to enable the catalog's taps') and names the follow-up path (poll catalog_enable_order's `job` block with `wait_seconds`) plus the approval alternative (poll `get_approval` instead of re-issuing).

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