Utility Matrix

Cloud Egress Cost Calculator

egress-cost-calculator

Read-onlyIdempotent

Use this when a user asks about monthly internet egress cost from daily request volume, average response size, provider, and CDN offload. Uses the same model as the browser calculator.

Input Schema

Name	Required	Description
`cdn_pct`	No	cdn expressed as a percentage.
`provider`	No	Cloud provider whose published pricing model should be applied.
`daily_requests`	Yes	daily requests used by this deterministic tool.
`avg_response_kb`	Yes	avg response kb used by this deterministic tool.

Output Schema

Name	Required	Description	Default
`cdn_pct`	Yes
`provider`	Yes
`cost_risk`	Yes
`next_step`	Yes
`rate_per_gb`	Yes
`free_tier_gb`	Yes
`next_step_url`	Yes
`why_follow_up`	Yes
`cdn_offload_gb`	Yes
`interpretation`	Yes
`daily_egress_gb`	Yes
`monthly_cost_usd`	Yes
`origin_egress_gb`	Yes
`affiliate_context`	No
`computation_basis`	Yes
`monthly_egress_gb`	Yes
`billable_egress_gb`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedOutput schema / properties / cdn_pct
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / required

Previous value: -[
-  "billable_egress_gb",
-  "cdn_offload_gb",
-  "computation_basis",
-  "cost_risk",
-  "daily_egress_gb",
-  "free_tier_gb",
-  "interpretation",
-  "monthly_cost_usd",
-  "monthly_egress_gb",
-  "next_step",
-  "next_step_url",
-  "origin_egress_gb",
-  "provider",
-  "rate_per_gb",
-  "why_follow_up"
-]New value: +[
+  "billable_egress_gb",
+  "cdn_offload_gb",
+  "cdn_pct",
+  "computation_basis",
+  "cost_risk",
+  "daily_egress_gb",
+  "free_tier_gb",
+  "interpretation",
+  "monthly_cost_usd",
+  "monthly_egress_gb",
+  "next_step",
+  "next_step_url",
+  "origin_egress_gb",
+  "provider",
+  "rate_per_gb",
+  "why_follow_up"
+]

Changed18 schema fields changedSep 28, 2026

addedInput schema / properties / avg_response_kb

Added value: +{
+  "description": "avg response kb used by this deterministic tool.",
+  "examples": [
+    1
+  ],
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / cdn_pct

Added value: +{
+  "description": "cdn expressed as a percentage.",
+  "examples": [
+    1
+  ],
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / daily_requests

Added value: +{
+  "description": "daily requests used by this deterministic tool.",
+  "examples": [
+    1
+  ],
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / provider

Added value: +{
+  "description": "Cloud provider whose published pricing model should be applied.",
+  "enum": [
+    "AWS",
+    "GCP",
+    "Azure",
+    "Cloudflare",
+    "DigitalOcean"
+  ],
+  "examples": [
+    "AWS"
+  ],
+  "type": "string"
+}

removedInput schema / properties / transfer_gb
```
Removed value: -{
-  "type": "number"
-}
```

changedInput schema / required

Previous value: -[
-  "transfer_gb"
-]New value: +[
+  "daily_requests",
+  "avg_response_kb"
+]

addedOutput schema / properties / billable_egress_gb
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / cdn_offload_gb
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / computation_basis
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / daily_egress_gb
```
Added value: +{
+  "type": "number"
+}
```
removedOutput schema / properties / effective_rate_per_gb
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / free_tier_gb
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / monthly_egress_gb
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / origin_egress_gb
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / provider
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / rate_per_gb
```
Added value: +{
+  "type": "number"
+}
```
removedOutput schema / properties / transfer_gb
```
Removed value: -{
-  "type": "number"
-}
```

changedOutput schema / required

Previous value: -[
-  "cost_risk",
-  "effective_rate_per_gb",
-  "interpretation",
-  "monthly_cost_usd",
-  "next_step",
-  "next_step_url",
-  "transfer_gb",
-  "why_follow_up"
-]New value: +[
+  "billable_egress_gb",
+  "cdn_offload_gb",
+  "computation_basis",
+  "cost_risk",
+  "daily_egress_gb",
+  "free_tier_gb",
+  "interpretation",
+  "monthly_cost_usd",
+  "monthly_egress_gb",
+  "next_step",
+  "next_step_url",
+  "origin_egress_gb",
+  "provider",
+  "rate_per_gb",
+  "why_follow_up"
+]

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"
+    },
+    "cost_risk": {
+      "type": "string"
+    },
+    "effective_rate_per_gb": {
+      "type": "number"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "monthly_cost_usd": {
+      "type": "number"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "next_step_url": {
+      "type": "string"
+    },
+    "transfer_gb": {
+      "type": "number"
+    },
+    "why_follow_up": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "cost_risk",
+    "effective_rate_per_gb",
+    "interpretation",
+    "monthly_cost_usd",
+    "next_step",
+    "next_step_url",
+    "transfer_gb",
+    "why_follow_up"
+  ],
+  "type": "object"
+}

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

TDQS

A3.6/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 safety profile requires no description support. The description contributes one genuine behavioral claim - parity with the browser calculator's model - which is useful for trusting the output, but says nothing about pricing basis, rounding, or currency.

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, no filler, with the usage trigger front-loaded and the model-provenance note trailing. Every clause carries information the agent can act on.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. Inputs are all enumerated and the deterministic nature is implied, but the description never states the pricing basis (published on-demand list prices) or what happens to provider/cdn_pct when omitted, which are minor but real gaps for a cost-figure 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 description coverage is 100% and provider is an enum, so every parameter is already documented in the schema. The description merely restates the four inputs (daily request volume, average response size, provider, CDN offload) in prose, adding no format, unit, or default information beyond the schema. Baseline 3 is appropriate.

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?

States a specific computation (monthly internet egress cost) plus the exact inputs that drive it, which cleanly separates it from cost siblings like ec2-cost-calculator or pipeline-cost-estimator. It stops short of naming any sibling it is not, so differentiation is inferred from the narrow domain rather than stated.

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 opening 'Use this when a user asks about...' is a concrete positive trigger, which is better than nothing. However there is no when-not guidance and no routing to alternatives such as ec2-cost-calculator for compute spend or cloud-waste-calculator, so the agent must infer the boundary itself.

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?