Skip to main content
Glama
Datris MCP Server

Datris MCP Server

catalog_enable_order

Get the order to enable a catalog's taps by dependency level, showing which taps are ready, blocked, tested, or landed, so you run sources before dependents.

Instructions

Read-only. The order to enable a catalog's taps in: taps grouped into levels, level 1 first (taps that read no other tap's tables), then the taps that read tables produced by level 1, and so on. A tap's dependencies are its declared dependsOn or, when it declares none, the taps the platform inferred from the tables its script queries. Per tap: hasPassingTest (last test run succeeded on the tap's current script; a test of an older script does not count), lastRealRunLanded (last real run landed records), blockedBy (dependencies that have not landed data yet) and ready. A tap whose sources have not landed data fails its test, so run the sources first. Taps on a dependency cycle are listed under cycles. Use it to answer "what order do I enable these in", e.g. after restore_catalog, where every tap is disabled with no data landed.

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

Input Schema

NameRequiredDescriptionDefault
catalogYesCatalog name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 up front, explains that a tap with unlanded sources will fail its test (so sources must run first), clarifies that hasPassingTest only counts a test of the current script, and notes that cycle members are reported separately under `cycles`. These are non-obvious semantics an agent could not derive from the name or schema.

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 safety profile ("Read-only") is front-loaded, then ordering logic, then per-field semantics, then the use case. It is long but dense, and the field-by-field explanation is justified because there is no output schema. Minor cost: it reads as one dense block rather than clearly separated clauses.

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 must define the return shape, and it does: level structure, the four per-tap fields, and the `cycles` bucket. Combined with the failure-ordering caveat and the restore_catalog scenario, an agent has everything needed to call it and interpret the result correctly.

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?

There is a single required parameter, `catalog`, and schema description coverage is 100% ("Catalog name."). The description adds no naming, format, or scoping detail beyond that, so the schema does all the work and the baseline of 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 description states precisely what the tool produces: the level-ordered sequence in which a catalog's taps should be enabled, plus per-tap readiness fields (hasPassingTest, lastRealRunLanded, blockedBy, ready) and any `cycles`. It also disambiguates from the write-side sibling by leading with "Read-only," so an agent can tell this is the planning/inspection call rather than the one that performs enablement.

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?

It gives an explicit trigger scenario: answer "what order do I enable these in", e.g. after restore_catalog when every tap is disabled with no data landed. That is a concrete when-to-use. It stops short of naming an alternative tool or stating when not to call it (e.g. when taps are already enabled and landed), leaving that to inference.

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