Skip to main content
Glama

Get cluster cost

get_cluster_cost
Read-only

Get what the current cluster costs now, as a list-price estimate from the cost metering: the monthly and hourly cost, the month to date and the projected month end, its parts (compute, storage, network and load balancers, control plane, and infrastructure such as bastions and standalone VMs), pricing coverage and confidence, and the costliest namespaces. unrequested_monthly_display is the compute no pod requests (allocatable capacity, control planes and autoscaled groups left out: requests, never measured usage, so do not call it idle or unused); unallocated_monthly_display is the part of the estimate no namespace's allocation carries (unrequested capacity, storage no namespace claims, network, control plane and infrastructure). When unpriced_volume_count is above zero, storage_monthly_display covers the priced volumes only and says how many are unpriced: storage costs at least that, and what the unpriced ones cost is unknown, not zero. A figure or count the snapshot did not record is null: unknown, not zero. Money is in the organisation's display currency and timestamps are UTC. A cluster with no current bill answers has_data false and no figure for now: one the metering has not priced within the last 26 hours (stopped, offline, or not priced yet), one whose node inventory went stale, or one whose newest snapshot priced nothing because no price covers what it bills. Its cost now is unknown, not zero, readiness.state says why, and stale_snapshot_at says when it was last priced past the window. When it was metered before, metered_month_to_date_display is what it was metered for this month in the hours the metering could price it (spend already measured, so a floor for the month, not its cost now), null when no hour of this month was metered, which is unknown, not zero. Estimates are derived from cloud list prices, not the customer's actual bill.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_cluster_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint annotation, the description discloses many behavioral traits: null means unknown rather than zero, has_data false occurs in specific stale/offline/unpriced conditions, metered_month_to_date is a floor rather than current cost, and unpriced storage makes the estimate partial. It also explains currency and UTC conventions.

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?

The purpose is front-loaded and most of the dense detail is justified because there is no output schema. The single long paragraph with nested parentheticals is harder to scan than necessary, and the repeated 'unknown, not zero' phrase adds minor redundancy.

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?

With no output schema, the description carries the full burden of explaining return values, including breakdown fields, coverage and confidence, costliest namespaces, has_data false cases, ready-state reasons, stale timestamps, and partial-storage semantics. It is complete for an agent to interpret the response correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already explains cluster_id and points to list_clusters for discovery. The description adds no additional meaning about the parameter itself; its value lies in return semantics, which is appropriate but does not exceed the baseline for fully documented parameters.

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?

The description opens with a specific verb, resource, and scope: what the current cluster costs now as a list-price estimate from cost metering. It implicitly separates itself from stack cost, fleet cost, and actual-bill reconciliation tools by naming the cluster-level list-price perspective.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied by 'current cluster' and 'list-price estimate, not the customer's actual bill,' which hints at when not to use it for billing reconciliation. However, it never explicitly names alternatives such as get_stack_cost, get_fleet_cloud_cost, or get_cost_reconciliation, so the agent must infer routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.