Get fleet cloud cost
get_fleet_cloud_costGet the cloud cost rollup of the current project - or of one project, or the whole organisation, with project_id - the same figures the portal's Cost page shows. scope says what was read; by_project splits the organisation-wide read per project, with an unattributed bucket for spend stamped with no project, and partial true means RBAC hid clusters so every figure is a floor. Returns the projected month-end, month-to-date and monthly run-rate totals in the organisation's display currency, generated_at (when the newest snapshot behind them was taken), the split by provider (cluster count and the same three figures each), and the costliest clusters with their confidence level. cluster_count, the run rate, the provider rows' cluster counts and run rates, and top_clusters cover the clusters metered in the last day whose node inventory is current; month-to-date and month-end also count what clusters spent this month before they were deleted, stopped reporting, had their node inventory go stale, were left unpriced (metered, but no price covers what they bill) or (on a project read) moved to another project, and so do the provider rows' month figures, under the provider of each one's last snapshot, so they sum to month-to-date. The unmetered block names those clusters with their spend, reason and last_snapshot_at and counts them per reason, and its summary is the line to quote for the spend no metered cluster accounts for. A cluster that stopped reporting or whose node inventory went stale may still be running, so what it cost since it was last metered is unknown and the month-end is a floor; a cluster left unpriced is still billing at a cost no price covers, so its cost is unknown too; a stale or unpriced cluster that metered nothing this month is listed with month_to_date_display null, never as free. unpriced_cluster_count counts the live clusters in scope with no price from the last day, the count a budget over the same clusters states: what they cost is unknown, not zero, so with any of them the run rate and month-end are floors, and unpriced_message is the line to quote; the unmetered block names the ones among them that were metered but priced nothing, with reason unpriced, ahead of the rest. has_data false means no cluster in scope is metered and no spend is recorded this month: nothing is priced yet, not that the fleet is free. It also carries a trend block over the last 30 days: the run rate at the start and now, and every day the set of priced clusters changed, naming the clusters that entered or left pricing - a coverage move, not spend; and an events block naming the biggest moves on the line (releases, node changes, stops and starts, executed decisions, coverage, resolved waste), each with how its delta was measured. available false means the block could not be read. Read-only. Use get_cluster_cost on a selected cluster for its per-namespace breakdown.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_fleet_cloud_cost"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | No | UUID of a project to read, or all for the whole organisation. Leave it out to read the project the conversation or token is in (the whole organisation while the organisation has no projects). list_projects has the ids. |