Skip to main content
Glama

TrueCalci

by com.truecalci
OverviewDiscussionsAdmin

Cloud egress cost (FinOps)

cloud_egress_finops
Read-onlyIdempotent

Analyze tiered AWS/GCP public cloud internet data transfer egress pricing versus Cloudflare Zero-Egress Bandwidth Alliance and edge caching proxies, quantifying monthly and annual infrastructure cost savings.

Behavior: Deterministic, idempotent calculation with zero external side effects. Calculates tiered AWS/GCP egress charges ($0.09/GB for first 10TB, $0.085/GB for next 40TB, $0.07/GB for next 100TB, $0.05/GB beyond). Models edge cache offload reduction and compares against Cloudflare zero-egress routing. Returns monthly and annual gross egress costs, post-cache costs, and total net savings.

Usage Guidelines: Use for cloud architecture budgeting, FinOps reviews, and evaluating CDN caching or Cloudflare migration economics. Do not use for LLM token pricing; use ai_token_arbitrage instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_of_dateYesCivil date YYYY-MM-DD selecting the monthly egress price pack. Required; only months with a published pack are answered (otherwise a structured refusal).
cacheHitRatioNoExpected CDN edge caching hit ratio as a decimal (0.0 to 1.0) or percentage (0 to 100%). Default is 0.85 (85%).
monthlyEgressGBNoMonthly public internet outbound data transfer volume in Gigabytes (GB) (e.g. 50000 for 50 TB). Must be positive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[
+  "as_of_date"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / as_of_date
      Added value: +{
+  "description": "Civil date YYYY-MM-DD selecting the monthly egress price pack. Required; only months with a published pack are answered (otherwise a structured refusal).",
+  "example": "2026-09-26",
+  "format": "date",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / cacheHitRatio / description
      Previous value: -"Projected CDN edge cache hit ratio (0.0 to 1.0 or 0 to 100%)"New value: +"Expected CDN edge caching hit ratio as a decimal (0.0 to 1.0) or percentage (0 to 100%). Default is 0.85 (85%)."
    • changedInput schema / properties / monthlyEgressGB / description
      Previous value: -"Monthly internet outbound data transfer in GB (e.g. 50,000 for 50TB)"New value: +"Monthly public internet outbound data transfer volume in Gigabytes (GB) (e.g. 50000 for 50 TB). Must be positive."
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark readOnly/idempotent/non-destructive; the description adds meaningful behavior beyond that: deterministic calculation, zero side effects, specific pricing tiers, modeling of cache offload, and the exact return categories. No contradiction with annotations exists.

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?

The description is well structured: a purpose sentence, a Behavior block, and a Usage block. It is slightly wordy in the opening phrase, but each sentence serves a distinct function and the key scoping/usage guidance is visible early.

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 read-only calculation tool with no output schema, it fully covers what an agent needs: inputs are schema-documented, behavior is deterministic, outputs are itemized (gross costs, post-cache costs, net savings), and usage vs alternatives is explicit.

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 coverage is 100%, so the baseline is 3. The description reinforces broad calculation context (tiered rates, cache reduction) but does not add much per-parameter meaning beyond what the schema already provides for as_of_date, cacheHitRatio, and monthlyEgressGB.

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?

The description names a specific verb ('analyze') tied to a precise resource: AWS/GCP egress pricing versus Cloudflare zero-egress, and states what it produces (monthly/annual savings). It also distinguishes itself from the financial/FinOps sibling cluster, especially via the explicit token-pricing exclusion.

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 gives explicit use cases (cloud architecture budgeting, FinOps reviews, CDN/Cloudflare migration evaluation) and an explicit when-not-to-use rule with the alternative named (ai_token_arbitrage). This is above the typical bar.

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

All TrueCalci toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources