Skip to main content
Glama

Get cost report

get_cost_report
Read-only

Read one cost report's rows, the detail get_fleet_cloud_cost and get_cloud_savings only summarise. report picks it: ledger (every cost decision that was approved, is running or ran, with what it was expected to save and what it measurably saved; the twin of ankra cost ledger), trend (the fleet's monthly run rate for each day of the window, and every day the set of priced clusters changed; the twin of ankra cost trend), waste (the open cloud waste findings: resources billing while nothing uses them, each with its monthly cost) and resolved_waste (what Ankra resolved inside the window, by kind). Reads the current project, or one project or the whole organisation with project_id; scope says what was read. Figures are in minor units of the display currency; null means unknown, not zero. Read-only: it resolves no finding and approves no decision.

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": {
      "report": "<report>"
    },
    "name": "get_cost_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNotrend and resolved_waste: the window in days (default 30; resolved_waste at most 90).
limitNoledger and waste: rows to return, 1 to 200 (default 50). The totals always cover every row.
reportYesWhich report to read.
cluster_idNowaste only: keep the findings of this cluster.
project_idNoUUID of a project to read, or all for the whole organisation. Leave it out to read the project the conversation or token is in. list_projects has the ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description still adds real context: figures are in minor units of the display currency, null means unknown rather than zero, and "it resolves no finding and approves no decision" preempts confusion with the sibling decision tools. It omits rate-limit or pagination behavior, so it stops short of the top score.

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?

Purpose and sibling differentiation are front-loaded, but the first sentence runs very long with cited CLI twins for each report. The dense parenthetical enumerations earn their place by disambiguating report values, though the structure could be tighter.

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 burden of describing return content and does so for all four reports, plus currency units, null semantics, and scope reporting. An agent has enough to call it and interpret the response correctly without further lookups.

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 goes further by explaining what each report value actually returns (e.g. ledger is the twin of `ankra cost ledger`, waste covers resources billing while unused) and notes that totals always span every row regardless of limit. The days/limit/cluster_id details largely duplicate 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?

Opens with a specific verb and resource ("Read one cost report's rows") and immediately distinguishes itself from siblings get_fleet_cloud_cost and get_cloud_savings by explaining that those "only summarise." The four report values are each given a concrete meaning, so an agent knows exactly what it is fetching.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this when the summarized totals from the sibling tools are insufficient, then tells which report to pick and what each contains, including the bounded window for resolved_waste. Scoping rules (current project, one project via project_id, or all) are stated rather than left to inference.

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.