Skip to main content
Glama

Get stack cost

get_stack_cost
Read-only

Get what a specific stack on the current cluster costs now: its share of the cluster's current estimate, from the namespaces the stack deploys into (the compute their requests are allocated plus the storage of their volumes), as a list-price estimate in the organisation's display currency. has_data false means no figure: the cluster has no current estimate (it was not priced within the last 26 hours), or none of it was attributed to the stack. Its cost is then unknown, not zero.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesThe name of the stack to get the cost for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only provide readOnlyHint, and the description adds real behavioral context: it is a list-price estimate (not billed actuals), currency is the organisation's display currency, and pricing is only valid if the cluster was priced within the last 26 hours. The has_data=false semantics — "unknown, not zero" — is exactly the kind of failure-mode disclosure agents need. It does not describe response shape beyond the flag, which keeps it off a 5.

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 is front-loaded in the first clause, and the second sentence covers the null case without padding. The first sentence is dense with parenthetical nesting, which costs some readability, but every clause carries distinct information (estimate basis, currency, attribution domain).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 must carry return semantics itself, and it does explain the cost figure, currency, and the has_data flag. What remains unstated is the rest of the response payload and whether a stack spanning multiple clusters requires separate calls — minor gaps for a simple two-parameter read tool.

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 coverage is 100% and both parameters are self-documented, so the baseline is 3. The description reinforces that cluster_id refers to the "current cluster" and that the cost is scoped to a named stack's namespaces, but adds no format, quoting, or lookup guidance beyond what the schema already says.

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?

States a specific verb and resource ("Get what a specific stack ... costs now") and precisely delimits the scope: the stack's attributed share of the cluster's current estimate, derived from its namespaces' compute requests and volume storage, in the organisation's display currency. An agent knows exactly what figure comes back and at what granularity.

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?

The word "now" and the per-stack framing imply when to use it (current point-in-time stack-level cost), but no sibling is named despite many adjacent cost tools (get_cluster_cost, get_namespace_cost_history, get_object_cost, get_fleet_cloud_cost, get_cost_reconciliation). Nothing tells the agent to prefer this over cluster-level or historical cost tools, so routing is 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.