Skip to main content
Glama
Datris MCP Server

Datris MCP Server

browse_unity_catalog

Browse Unity Catalog one level per call to list catalogs, schemas, tables, or columns and tags for a Databricks secret. Check whether data already exists before creating a pipeline.

Instructions

Browse what a Databricks Platform secret can already see in Unity Catalog, one level per call: no catalog lists catalogs; catalog lists its schemas; catalog + schema lists tables; adding table returns its columns (name, type, comment) and tags. Use it before creating a Databricks pipeline to check whether the data already exists. Discover the secret name with list_platform_secrets. Tables carrying the datris_pipeline tag were loaded by that Datris pipeline (query them with query_databricks and that pipeline). If tag lookups are not permitted for the secret, tagsAvailable is false and browsing still works. The SQL warehouse comes from the warehouse argument, else the secret's optional warehouse field, else an existing Databricks pipeline using the secret. A stopped SQL warehouse auto-starts on the first call, which can take 5-20 seconds (longer for classic warehouses). Read-only; catalog and schema listings are cached for 5 minutes.

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": {
      "secret": "<secret>"
    },
    "name": "browse_unity_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableNoTable within `catalog`.`schema` to describe (optional; requires catalog and schema).
schemaNoSchema within `catalog` to list tables of (optional; requires catalog).
secretYesName of the Databricks Platform secret (from list_platform_secrets).
catalogNoUnity Catalog catalog to list schemas of (optional).
warehouseNoSQL warehouse ID to run the metadata queries on (optional; see description for the fallback order).

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, the description carries the full burden and does so: it declares read-only behavior, 5-minute caching of catalog and schema listings, warehouse resolution fallback order, and a 5-20 second auto-start penalty on stopped warehouses. It also discloses a partial-failure mode (`tagsAvailable` false) that still allows browsing, which is exactly the kind of non-obvious behavior an agent needs to plan around.

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 level-by-level semantics that matter most for invocation, then layers operational details. It is dense and every sentence is substantive, though the tag/warehouse material runs long enough that an agent skimming may lose the core level mapping buried mid-paragraph.

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 5-parameter read tool with no annotations and no output schema, this covers the full decision surface: level semantics, prerequisites, latency and caching, credential-scoped limitation on tags, and warehouse selection. Nothing an agent needs in order to call it correctly, or to interpret a degraded response, 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 already 100%, so the schema documents each parameter individually; the description's added value is compositional - it spells out how `catalog`, `schema`, and `table` nest into successive browse levels, and how `warehouse` resolves via a three-step fallback. It stops short of adding format or ID examples, which keeps it at a strong 4 rather than a 5.

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?

Opens with a specific verb and resource ('Browse what a Databricks Platform secret can already see in Unity Catalog') and immediately disambiguates by mapping argument combinations to browse levels, so an agent can predict the exact result shape of each call. It also names the sibling used for secret discovery (list_platform_secrets) and the sibling used to read the resulting tables (query_databricks).

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 ('before creating a Databricks pipeline to check whether the data already exists') plus the prerequisite chain (discover the secret name with list_platform_secrets). It also routes the agent away from this tool for row-level reads by pointing at query_databricks, and explains the degraded path when tag lookups are not permitted.

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