Skip to main content
Glama
Datris MCP Server

Datris MCP Server

query_databricks

Run read-only SQL queries against a Databricks pipeline's destination to verify loaded data or discover schemas and tables; omit SQL to preview the target table.

Instructions

Run a read-only query against the Databricks workspace a pipeline loads into. Pass the pipeline name; the server resolves the workspace, credentials, SQL warehouse, and catalog from the pipeline's config — same connection the loader uses, credentials never leave the server. Only works for pipelines whose destination is Databricks (database with useDatabricks=true). Allowed statements: SELECT (WITH/CTE), SHOW, and DESCRIBE — LIMIT is auto-appended to SELECTs. Omit sql to preview the pipeline's destination table (the 'did my load land?' check). Metadata discovery uses the same tool — there are no separate list_databricks_* tools: SHOW CATALOGS, SHOW SCHEMAS IN <catalog>, SHOW TABLES IN <catalog>.<schema>, DESCRIBE TABLE <catalog>.<schema>.<table>, or query .information_schema.columns. Queries run on the customer's SQL warehouse (which costs them compute) — keep them targeted and let the default LIMIT stand unless the user asks for more. If the warehouse is stopped, the first query auto-starts it and may take longer.

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": {
      "pipeline": "<pipeline>"
    },
    "name": "query_databricks"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlNoRead-only statement: SELECT/WITH, SHOW, or DESCRIBE. Omit to preview the pipeline's destination table.
limitNoMaximum rows to return (default: 100). Pass -1 for unlimited.
pipelineYesPipeline name (from list_pipelines). Must have a Databricks destination.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 discloses read-only enforcement, the allowed statement whitelist, that LIMIT is auto-appended to SELECTs, that credentials never leave the server, that queries consume the customer's warehouse compute, and that a stopped warehouse auto-starts with added latency. These are exactly the operational traits an agent needs before calling.

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 and scope, then constraints, then cost/latency caveats — a sensible order. It is on the long side and the metadata-discovery sentence enumerating four SHOW/DESCRIBE forms is dense, but every sentence carries actionable information rather than filler.

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?

No output schema and no annotations, yet the description still covers scope, credentials, statement limits, cost, latency, and the preview behavior. Nothing an agent needs in order to invoke this correctly 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 is 3, but the description adds real meaning: it explains that `pipeline` is resolved server-side into workspace, credentials, warehouse and catalog, and that `limit` interacts with the auto-appended LIMIT clause ('let the default LIMIT stand'). The `sql` semantics are largely restated from the schema.

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 (run a read-only query), a specific resource (the Databricks workspace a pipeline loads into), and a hard scope boundary (only pipelines whose destination is Databricks, useDatabricks=true). An agent can distinguish this from query_postgres/query_snowflake purely from the destination constraint.

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?

Gives concrete when-to-use cases: the 'did my load land?' check via omitting `sql`, and metadata discovery, explicitly noting there are no separate list_databricks_* tools and spelling out the SHOW/DESCRIBE forms to use instead. It also gives a when-not condition (non-Databricks destinations). It stops short of naming the sibling query_* tools as the alternative for other destinations, leaving that inference to the agent.

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