Utility Matrix

Cloud Waste Calculator

cloud-waste-calculator

Read-onlyIdempotent

Use when a user asks about cloud waste, idle resources, or unattached storage. Given monthly cloud bill and idle/oversized percentages, returns waste estimate and tier.

Input Schema

Name	Required	Description
`idle_pct`	No	idle expressed as a percentage.
`oversized_pct`	No	oversized expressed as a percentage.
`monthly_cloud_bill`	Yes	monthly cloud bill used by this deterministic tool.
`unattached_volumes_count`	No	unattached volumes count used by this deterministic tool.

Output Schema

Name	Required	Description	Default
`next_step`	Yes
`waste_pct`	Yes
`annualized`	Yes
`do_savings`	Yes
`idle_waste`	Yes
`output_tier`	Yes
`monthly_cost`	Yes
`signal_value`	Yes
`next_step_url`	Yes
`why_follow_up`	Yes
`interpretation`	Yes
`oversized_waste`	Yes
`unattached_cost`	Yes
`affiliate_context`	No
`computation_basis`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 28, 2026
- addedInput schema / properties / idle_pct / description
```
Added value: +"idle expressed as a percentage."
```
- addedInput schema / properties / idle_pct / examples
```
Added value: +[
+  1
+]
```
- addedInput schema / properties / monthly_cloud_bill / description
```
Added value: +"monthly cloud bill used by this deterministic tool."
```
- addedInput schema / properties / monthly_cloud_bill / examples
```
Added value: +[
+  1
+]
```
- addedInput schema / properties / oversized_pct / description
```
Added value: +"oversized expressed as a percentage."
```
- addedInput schema / properties / oversized_pct / examples
```
Added value: +[
+  1
+]
```
- addedInput schema / properties / unattached_volumes_count / description
```
Added value: +"unattached volumes count used by this deterministic tool."
```
- addedInput schema / properties / unattached_volumes_count / examples
```
Added value: +[
+  1
+]
```

Changed1 schema field changedJul 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "affiliate_context": {
+      "additionalProperties": false,
+      "properties": {
+        "affiliate": {
+          "type": "string"
+        },
+        "cta_label": {
+          "type": "string"
+        },
+        "disclosure": {
+          "type": "string"
+        },
+        "framing": {
+          "type": "string"
+        },
+        "posture": {
+          "enum": [
+            "secondary"
+          ],
+          "type": "string"
+        },
+        "slot_id": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        },
+        "variant": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "affiliate",
+        "cta_label",
+        "disclosure",
+        "framing",
+        "posture",
+        "slot_id",
+        "url",
+        "variant"
+      ],
+      "type": "object"
+    },
+    "annualized": {
+      "type": "number"
+    },
+    "computation_basis": {
+      "type": "string"
+    },
+    "do_savings": {
+      "type": "number"
+    },
+    "idle_waste": {
+      "type": "number"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "monthly_cost": {
+      "type": "number"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "next_step_url": {
+      "type": "string"
+    },
+    "output_tier": {
+      "type": "string"
+    },
+    "oversized_waste": {
+      "type": "number"
+    },
+    "signal_value": {
+      "type": "number"
+    },
+    "unattached_cost": {
+      "type": "number"
+    },
+    "waste_pct": {
+      "type": "number"
+    },
+    "why_follow_up": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "annualized",
+    "computation_basis",
+    "do_savings",
+    "idle_waste",
+    "interpretation",
+    "monthly_cost",
+    "next_step",
+    "next_step_url",
+    "output_tier",
+    "oversized_waste",
+    "signal_value",
+    "unattached_cost",
+    "waste_pct",
+    "why_follow_up"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 13, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJun 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safe/pure-calculator profile is fully covered by structured data. The description adds that it produces a 'waste estimate and tier', but that return detail is also covered by the output schema, so incremental behavioral disclosure is thin. A 3 reflects adequate but minimal added context given the low bar set by annotations.

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

Conciseness5/5

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

Two sentences, zero waste, with the usage trigger front-loaded before the input/output summary. Nothing superfluous and nothing buried.

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?

For a deterministic calculator with a present output schema and fully described parameters, the description covers when to invoke it, what it consumes, and what it returns. The only gap is that it does not address how the optional inputs (unattached volumes vs. percentages) combine or whether results are exhaustive.

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 description coverage is 100%, so the schema already documents all four parameters, and the baseline is 3. The description mentions 'monthly cloud bill and idle/oversized percentages' but omits unattached_volumes_count and adds no syntax, unit, or interaction detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource ('returns waste estimate and tier' for a cloud-waste calculation) and scopes it with 'cloud waste, idle resources, or unattached storage', which distinguishes it from cost-adjacent siblings such as ec2-cost-calculator and rightsizing-calculator. It stops short of explicitly contrasting those siblings, so it is clear but not maximally differentiated.

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?

The opening 'Use when a user asks about cloud waste, idle resources, or unattached storage' gives concrete trigger conditions an agent can pattern-match on. It does not name exclusions or point to alternatives (e.g., rightsizing-calculator for pure rightsizing questions), leaving some routing ambiguity among the many cost calculators.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Utility Matrix tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?