Skip to main content
Glama

list_savings_recommendations

Read-onlyIdempotent

List active cost-reduction recommendations for this account. Most come from each provider's own already-computed engine (AWS Cost Explorer, Azure Advisor, GCP Recommender); rows with source = plutus are computed by Plutus itself (rightsizing, and misconfiguration below). type is one of: terminate (an idle resource to shut down), modify (an overprovisioned one to downsize), commitment_savings_plan or commitment_reservation (a commitment worth buying — an AWS Savings Plan / Reserved Instance, Azure reservation or savings plan, or GCP committed use discount), or misconfiguration. Commitment rows have no current_instance_type/recommended_instance_type — they are a purchase, not an instance swap; their term, payment option, lookback window and hourly commitment are in detail. Only one term/payment/lookback variant per commitment is surfaced (AWS: 30-day lookback, 1-year, no upfront — Cost Explorer's own console default), so do not report these as the only commitment options available. Plutus also computes misconfiguration rows (source = plutus), the findings: a known costly setting found from billing lines (detail.scope = account) or an idle or orphaned resource found in the inventory (detail.scope = resource, with provider_resource_id). Their detail carries reason, fix, reference_url, confidence, spend_usd, impact_basis (upper_bound means the saving is a ceiling, at most that figure, not an estimate; say "up to". resource_cost means what the resource itself costs a month, not a saving from changing it; price_difference means an estimated saving from changing a setting, a share of the resource's own monthly cost, for example gp2 to gp3). A resource finding with detail.price_source = list_price is priced from AWS list prices because nothing is billed against it yet: call it an estimate, not a measured cost, and say it will be replaced by the billed figure, impact_unknown (true means the saving cannot be estimated, so estimated_monthly_savings_cents of 0 is NOT a $0 saving), where (service, region, usage types) and verify (console links and manual steps to confirm and fix it). Triage them like any recommendation: dismiss, mark acted-on, or ticket. Mirrors GET /api/accounts/:accountId/savings-recommendations. Each recommendation carries the provider's own figure in its own currency; the total is in USD (stated in the response's currency field), since providers may bill in different ones. total_estimated_monthly_savings_cents is the firm total only: it leaves out upper_bound findings, which are reported separately as upper_bound_findings ({ count, max_monthly_cents }): say "N findings, up to $X/month", never add that into the total.

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": "list_savings_recommendations"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly these recommendation types, comma-separated (for example "misconfiguration" for the findings)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Only these recommendation types, comma-separated (for example \"misconfiguration\" for the findings)",
      +  "maxLength": 300,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), yet the description adds substantial context beyond them: the upstream source of each row (Cost Explorer/Advisor/Recommender vs `plutus`), the caveat that only one commitment term/payment/lookback variant is surfaced, and the semantics of `impact_basis`, `impact_unknown`, and `price_source`. It also discloses the total's exact scope — `upper_bound` findings excluded and reported separately — which prevents a real reporting error.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the purpose, and most sentences carry operational value, but the body is one dense block of nested parentheticals and backticked field names. The type enumeration, commitment caveat, misconfiguration semantics, and total-scope rule would be far easier to scan as separate lines.

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 must carry the return-value burden — and it does: it documents `source`, `type`, `detail.*` fields, per-provider `currency` versus the USD total, and the split between `total_estimated_monthly_savings_cents` and `upper_bound_findings`. Relative to the tool's complexity, nothing an agent needs to interpret the response 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?

Schema coverage is 100% and the single `type` parameter is already documented in the schema, so the baseline is 3. The description goes further by explaining what each filterable type actually means (including that `misconfiguration` returns the `plutus`-sourced findings), adding genuine meaning beyond the schema's terse 'comma-separated' note.

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+resource+scope: 'List active cost-reduction recommendations for this account.' It then enumerates the `type` values (terminate, modify, commitment_savings_plan, commitment_reservation, misconfiguration), which makes it clearly distinct from the sibling `list_tag_recommendations` without needing to name it.

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 description gives rich guidance about what to do with the results ('Triage them like any recommendation: dismiss, mark acted-on, or ticket') and how to report them, but it never states when to call this tool versus the tag-recommendation sibling or when to exclude a type. Usage is implied by the resource scope rather than explicitly routed.

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.

Resources