estimate_cost

2 MCP servers expose a estimate_cost tool: Databricks Field Guide by TechFabric and Tomorrow Central: Cloud Cost Sentinel. Their input schemas differ, so compare them below before picking one.

Servers exposing estimate_cost

• Databricks Field Guide by TechFabricB · 73HTTP

  From the publisher:Estimate a Databricks workload's monthly cost from the figures the Field Guide states (list prices per DBU by compute type, DBUs an hour by SQL warehouse size and classic instance type, model serving prices for pay-per-token, provisioned throughput, GPU and CPU serving, Apps and Genie rates, the Lakebase floor, storage), as a range with its assumptions, and the price per unit under unit_prices. Ev

  Parameter	Type	Description
  workload*	string	jobs, all_purpose (interactive notebooks), sql_warehouse, apps, genie, lakebase, model_serving or storage
  compute	string	jobs and all_purpose: serverless or classic; sql_warehouse: serverless, pro, classic, or lakehouse_rt (Beta) priced from DBUs you give
  size	string	apps: medium (the default), large or xlarge; sql_warehouse: the t-shirt size, 2x-small, x-small, small, medium, large, x-large, 2x-large, 3x-large, 4x-large, 5x-large (DBUs an hour per cluster, from t
  dbus_per_hour	number	DBUs the compute uses an hour, when the guide has no figure for its shape (a serverless job, an instance type it does not list): from system.billing.usage or Databricks' pricing calculator
  clusters	integer	sql_warehouse: clusters running (default 1)
  max_clusters	integer	sql_warehouse: the most clusters it scales out to; the estimate ranges from clusters to max_clusters
  instance_type	string	jobs or all_purpose, classic: the AWS instance type (m5.xlarge, m5.2xlarge, m6i.xlarge, m7i.xlarge, r5.xlarge, c5.2xlarge, i3.xlarge, i3.2xlarge are in the guide)
  instances	integer	jobs or all_purpose, classic: instances in the cluster, the driver counted as one; model_serving cpu: Medium configurations
  serving	string	model_serving: pay_per_token, provisioned_throughput, gpu or cpu (omit for every price the guide states)
  model	string	model_serving, pay_per_token or provisioned_throughput: the model, as in 'Llama 3.3 70B' or 'claude-sonnet-5.5'
  input_tokens_millions	number	model_serving, pay_per_token: input tokens a month, in millions
  output_tokens_millions	number	model_serving, pay_per_token: output tokens a month, in millions
  model_units	integer	model_serving, provisioned_throughput: model units (default 50, the block the rates are quoted for; a reservation takes multiples of 50 and bills every hour of its term)
  reservation	string	model_serving, provisioned_throughput: on_demand, 1_month or 3_month
  dbus_per_month	number	Or the DBUs a month outright
  hours_per_day	number
  days_per_month	number	Days it runs a month (default 30 with hours_per_day)
  hours_per_month	number
  users	integer	genie: the people using it
  dbus_per_user	number	genie: each user's Genie DBUs a month

  Install Databricks Field Guide by TechFabric →
• Tomorrow Central: Cloud Cost SentinelC · 40HTTP

  From the publisher:Price a list of cloud components at real list prices. No account or signup. Use this when the user can name the pieces: "two m5.large servers, a Postgres database and a load balancer in Mumbai". If they cannot name the pieces, use `describe_workload` instead, which asks in units a person actually has. `items` is a list of `{"component": "<id>", "params": {...}}`. Get the ids and each component's p

  Parameter	Type	Description
  items*	array
  region*	string
  term	string

  Install Tomorrow Central: Cloud Cost Sentinel →

Tool lists are read from the live servers (or, for packaged servers, from their documentation) each morning, so this reflects what they exposed at the last refresh. Search all tools.