Skip to main content
Glama
markatdataandbeyond

DBU Waste Finder

by markatdataandbeyond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATABRICKS_HOSTYesDatabricks workspace URL used by the MCP server to read system tables.
DATABRICKS_TOKENYesRead-only Databricks token or service principal token used to read system tables.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
cost_summaryA

Orient on spend: total list-price cost, cost per product and per day for the last days days (integer 1..365). Read-only; list price, not your discount. USD totals cover priced usage only — when a SKU has no list price, usd_complete is false and unpriced_skus lists it. Use before find_waste when you need the overall bill shape.

top_cost_driversA

Top 20 jobs, warehouses and clusters by list-price cost over the last days days (1..365). Read-only; returns {rows, usd_complete, unpriced_skus}. Use to answer "what spent the most?" before drilling into waste with find_waste. List price only — not applied discounts.

cost_review_reportA

One markdown cost-review report for the last days days (1..365) from cost_summary + top_cost_drivers + find_waste: executive summary, top drivers, waste findings with estimated list-price amounts, and proposed fixes. max_autotermination_minutes / warehouse_idle_pct / max_rows are forwarded to find_waste. Read-only; proposals only — nothing is applied. Returns {days, markdown, measured_saving_usd, projected_30d_usd}.

find_wasteA

Find wasted DBUs over the last days days (1..365). Read-only; never changes the workspace. Returns measured_saving_usd / measured_waste_dbu, observation_days, projected_30d_usd/_dbu (= measured / observation_days * 30; withheld below 3 days) and low_confidence (< 7 days). Classic: jobs on all-purpose, clusters with auto-termination off or above max_autotermination_minutes (default 60), idle/oversized clusters. Serverless: warehouses with no/long auto-stop, idle warehouses (idle_pct ≥ warehouse_idle_pct, default 80), serverless jobs incl. failed-run share. Delta: needs OPTIMIZE / VACUUM / over-frequent OPTIMIZE (proposals only). At most max_rows rows per check (1..1000). USD is None when unknown; failed checks go under errors with the table and the GRANT/fix — totals are never a fake $0.

explain_cost_spikeA

Explain a one-day cost spike: which jobs/warehouses/clusters drove list-price cost on date (YYYY-MM-DD UTC billing day = system.billing.usage.usage_date) vs the prior 7-day daily average. Read-only. Use when the user asks "why did Tuesday cost more?" after cost_summary.

propose_fixA

Propose a fix as a unified diff (Asset Bundle YAML) or reviewable SQL — never applied. issue: 'all_purpose_job' (move tasks off existing_cluster_id onto a job cluster), 'no_autotermination' (set resources.clusters..autotermination_minutes), 'warehouse_autostop' (set resources.sql_warehouses..auto_stop_mins, default 10), or Delta (delta_optimize|delta_vacuum|delta_zorder|delta_predictive_optimization| delta_overfrequent_optimize) which returns SQL (resource_key = catalog.schema.table; for delta_zorder pass columns as comma-separated node_type_id; for delta_vacuum pass retention hours as minutes, default 168 / min 7 days). Pass cluster_id from find_waste for cluster fixes — a deleted cluster is refused. bundle_yaml may be empty for Delta issues.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct resource and question: cost_summary (bill shape), top_cost_drivers (top spenders), cost_review_report (composite deliverable), find_waste (waste detection), explain_cost_spike (single-day cause), and propose_fix (remediation output). Descriptions explicitly establish call ordering and dependency (e.g. use before find_waste, after cost_summary), so an agent can select confidently.

Naming Consistency4/5

All names are snake_case and readable, but conventions mix noun phrases (cost_summary, top_cost_drivers, cost_review_report) with verb_noun phrases (find_waste, explain_cost_spike, propose_fix). The deviation is minor and does not impede understanding.

Tool Count5/5

Six tools is well-scoped for a cost-review/waste-finder server, with each tool earning its place across orient, drill-down, report, explanation, and remediation. No redundant or trivial entries.

Completeness4/5

The surface covers orientation, drill-down, spike explanation, comprehensive reporting, and fix proposals, forming a coherent read-only workflow. Minor gaps remain, such as no direct entity-detail lookup (specific job/cluster metadata) or validation of proposed fixes, but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources