Skip to main content
Glama

Get cost settings

get_cost_settings
Read-only

Get the organisation's cloud cost pricing settings: the display currency (usd, eur or gbp) every cost figure is shown in, the effective discount in percent applied on top of provider list prices (approximating committed-use or enterprise agreements), include_network_egress_estimate (stored, not metered yet: no figure includes network egress today, whichever way it is set), and analysed_cluster_limit, how many of the costliest priced clusters the savings model analyses. Returns the defaults (eur, 0, egress off, limit 8) when nothing was ever configured. Read-only; read this before update_cost_settings.

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_cost_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses substantive behavior: default values when nothing is configured (eur, 0, egress off, limit 8), that the discount approximates committed-use or enterprise agreements, and the important caveat that include_network_egress_estimate is stored but not metered so no figure currently includes egress. That last point materially prevents a misreading of the returned data.

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?

Front-loaded with the purpose, then the fields in order, then the defaults, then the routing instruction. It is a single long run-on sentence with several parentheticals, which makes it denser than necessary, but every clause (including the egress caveat) carries information an agent needs.

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?

There is no output schema, so the description carries the burden of describing the return shape — and it does, naming each setting, its units (percent, currency codes), and the fallback defaults. Combined with the read-only annotation and the explicit sequencing toward update_cost_settings, nothing needed to call or interpret this tool is missing.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing for the description to compensate for. The description instead spends its words on the semantics of the returned fields, which is valuable but is not parameter guidance.

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 the organisation's cloud cost pricing settings') and enumerates exactly what the returned settings are: display currency, effective discount, include_network_egress_estimate, and analysed_cluster_limit. Unlike the many cost-adjacent siblings (get_cost_budgets, get_cost_autopilot, get_cluster_cost), it is unambiguously about the pricing configuration object itself.

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

Usage Guidelines4/5

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

Explicitly labels the operation read-only and instructs 'read this before update_cost_settings', which names the write counterpart and establishes ordering. It does not exclude any adjacent read tools (e.g. get_cost_autopilot, get_cost_budgets) as alternatives, so it falls just short of a full when/when-not statement.

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.