Skip to main content
Glama

Update cost settings

update_cost_settings
Destructive

Replace the organisation's cloud cost pricing settings: the display currency (usd, eur or gbp), the effective discount in percent (0-100) applied on top of provider list prices, and include_network_egress_estimate, which is stored, not metered yet: no figure includes network egress today, whichever way it is set. This is a full replace of those three - call get_cost_settings first and restate every value, changing only what the user asked for. analysed_cluster_limit (1-50, default 8) sets how many of the costliest priced clusters the savings model analyses; it is optional, and omitting it keeps the current limit. Organisation admins only (billing.manage). Every fleet, cluster and namespace figure re-prices on its next read; reversible by setting the previous values back.

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": {
      "currency": "<currency>",
      "effective_discount_pct": "<effective_discount_pct>"
    },
    "name": "update_cost_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYesDisplay currency for every cost figure.
analysed_cluster_limitNoHow many of the costliest priced clusters the savings model analyses (default 8). Optional: omit it to keep the current limit.
effective_discount_pctYesEffective discount in percent applied on top of list prices; 0 shows list price.
include_network_egress_estimateNoWhether figures should carry a network egress estimate once egress is metered. Stored, not metered yet: no figure includes network egress today, whichever way it is set. Defaults to false when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include_network_egress_estimate / description
      Previous value: -"Include an estimated network egress component. Defaults to false when omitted."New value: +"Whether figures should carry a network egress estimate once egress is metered. Stored, not metered yet: no figure includes network egress today, whichever way it is set. Defaults to false when omitted."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds substantive context beyond them: it is a full replace rather than a partial patch, it re-prices every fleet, cluster and namespace figure on next read, and it is reversible by restating previous values. The egress caveat (stored but never metered today) prevents a false expectation about output. Minor gap: it does not say what the response contains or whether concurrent settings changes are rejected.

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?

One dense paragraph with the write/replace semantics and the get-first procedure front-loaded, and it stays tight for the amount of behaviour it has to convey. It loses a little by repeating the egress "stored, not metered yet" wording verbatim from the schema and by cramming the admin-requirement clause mid-sentence.

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?

For a destructive, non-idempotent mutation with no output schema, the agent is given everything needed: full-replace obligation, prerequisite read call, permission scope, blast radius (all cost figures re-price), reversibility path, and the egress caveat. Nothing material is left to inference.

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 all four parameters are already documented; baseline would be 3. The description nonetheless adds the critical cross-parameter rule that this is a full replace and every value must be restated, plus the note that analysed_cluster_limit is optional and omission preserves the current limit. That operational meaning is not derivable from the per-field schema alone.

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?

"Replace the organisation's cloud cost pricing settings" names a specific verb (replace) and resource, then enumerates exactly which fields change: currency, effective discount, and include_network_egress_estimate. It is immediately distinguishable from get_cost_settings, which it names as the read counterpart.

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?

It states the operative procedure explicitly: call get_cost_settings first and restate every value, changing only what the user asked for. It also states the precondition (organisation admins only, billing.manage) and the optional-parameter behaviour, so the agent knows both when to call it and how to call it safely.

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.