Skip to main content
Glama
Datris MCP Server

Datris MCP Server

set_catalog

Set or clear a catalog grouping label on an existing pipeline or tap only when a user explicitly asks to organize work under a named catalog.

Instructions

Set or clear the catalog grouping label on an existing pipeline or tap. ONLY call this when the user has explicitly asked to organize work under a named catalog. Do NOT call it proactively — catalogs are a user-chosen organizational convention; assigning one for them puts the pipeline/tap into a taxonomy they didn't ask for. Pass exactly one of pipeline or tap to identify the target. Pass catalog to set the label, or omit it (or pass an empty string) to clear it. Survives subsequent re-ingests — datris ingest no longer rewrites an existing pipeline's config. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
tapNoTap name to update. Mutually exclusive with `pipeline`.
reasonNoOptional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it.
catalogNoCatalog label. Omit or pass an empty string to clear the label.
pipelineNoPipeline name to update. Mutually exclusive with `tap`.

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 provided, the description carries the full burden and does so: it discloses persistence semantics ('survives subsequent re-ingests'), the approval-gated behavior returning status `pending_approval` with an `approvalId`, and the polling protocol. It also warns against re-issuing the action, which is exactly the kind of mutation hazard an agent needs to know.

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?

Front-loaded with purpose, then constraints, then approval mechanics — a sensible ordering with no filler sentences. It is on the longer side, but each sentence contributes a distinct rule (proactivity ban, target exclusivity, clear semantics, persistence, approval flow).

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?

For a four-parameter mutation with no annotations and no output schema, the description covers everything needed to call it correctly: target selection, clearing behavior, durability, and the full approval outcome path. Nothing an agent would need to invoke or recover from this tool is missing.

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 would be 3; the description adds the mutual-exclusion constraint ('Pass exactly one of `pipeline` or `tap`'), which the schema only asserts per-parameter and does not enforce structurally since no parameters are required. It also restates the clear-via-omission or empty-string rule for `catalog`. The `reason` parameter is left to the schema, a minor gap.

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 pair (set/clear) plus the exact resource (catalog grouping label) and scope (existing pipeline or tap). An agent can immediately distinguish this from sibling catalog tools like rename_catalog or delete_catalog, which act on catalogs themselves rather than on pipeline/tap labels.

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 bounds invocation: 'ONLY call this when the user has explicitly asked to organize work under a named catalog' and 'Do NOT call it proactively,' with the rationale given. It also supplies the correct follow-up path when approval is required, naming get_approval and wait_seconds as the next steps instead of re-issuing the call.

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