Skip to main content
Glama
Datris MCP Server

Datris MCP Server

rename_catalog

Rename a catalog in one server-side operation, relabelling all associated taps and pipelines and moving the empty-catalog placeholder when explicitly requested.

Instructions

Rename a catalog: every tap and pipeline labelled with catalog is relabelled to new_name in one server-side operation, and the empty-catalog placeholder moves with it. Call this ONLY when the user has explicitly asked to rename that catalog — never to emulate a rename by calling set_catalog on each item. new_name must not already exist: a rename never merges catalogs and is refused if the target exists. To combine two catalogs, move their items with set_catalog. Uncataloged cannot be renamed, and new_name must use letters, digits, '_' and '-' only. Items that could not be moved come back under failed (the rest still move); report them to the user. API keys whose capabilities are scoped to the old catalog name are listed under affectedKeys — they keep the old scope and no longer match the renamed items, so tell the user an administrator may need to update those keys. 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>",
      "new_name": "<new_name>"
    },
    "name": "rename_catalog"
  }
}

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.
catalogYesCurrent catalog name.
new_nameYesNew catalog name (letters, digits, '_' and '-').

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 supplied the description carries the full burden and does so: it discloses the no-merge refusal rule, partial-failure semantics (unmoved items return under `failed` while the rest still move), and a non-obvious side effect where API keys scoped to the old name keep the old scope and appear under `affectedKeys`. It also describes the approval interlock in detail — the call returns `pending_approval` with an `approvalId` rather than acting, and the agent must poll `get_approval` with `wait_seconds` instead of re-issuing.

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 the core effect and the hard usage constraint, and nearly every sentence adds operational value (failure handling, key scoping, approval recovery). It is a dense single block of prose, however, and the approval-polling passage is long enough that breaking it into discrete constraints would scan faster; nothing is truly redundant.

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 are no annotations and no output schema, so the description must cover both safety and return shapes — and it does, naming `failed`, `affectedKeys`, `pending_approval`, and `approvalId`. For a destructive-with-side-effects mutation, an agent has everything needed to call it, report partial failures, warn about broken key scopes, and handle the approval path.

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, but the description adds semantics the schema does not: `new_name` must not already exist, a rename never merges, and the charset restriction is reinforced in prose. It does not explain the `reason` parameter, though the schema already documents its audit-log and approval-display purpose.

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 ("Rename a catalog") plus the exact observable effect: every tap and pipeline labelled with `catalog` is relabelled to `new_name` in one server-side operation and the empty-catalog placeholder moves too. It explicitly distinguishes itself from `set_catalog`, so an agent can separate rename from item-level relabelling without opening another 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?

Gives an explicit when-to-use rule ("ONLY when the user has explicitly asked to rename that catalog"), an explicit when-not rule ("never to emulate a rename by calling set_catalog on each item"), and names the correct alternative for the adjacent intent ("To combine two catalogs, move their items with set_catalog"). Preconditions are also spelled out: the target name must not already exist, and Uncataloged cannot be renamed.

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