sample-aws-pricing-calculator-mcp 1.2.1 → 1.2.4

package/README.md

@@ -9,7 +9,7 @@
 - **Build estimates from natural language** - agent constructs the estimate via MCP tools; the server saves it to AWS Pricing Calculator and returns a shareable URL.
 - **No AWS credentials required** - uses public, unauthenticated calculator.aws CDN endpoints.
 - **Live service definitions** - fetches the AWS Pricing Calculator manifest at runtime (~436 services).
-- **Verified Configs Catalog** - 16 per-service entries declaring the smallest config that produces a priced estimate, with documented gotchas.
+- **Verified Configs Catalog** - 18 per-service entries declaring the smallest config that produces a priced estimate, with documented gotchas.
 - **Lint refusal before save** - refuses estimates the calculator would render read-only or required-input, with actionable recovery hints.
 - **Import existing estimates** - download by URL or ID as JSON (for region swaps, modifications) or Markdown (for LLM analysis).
 - **Two transport modes** - stdio (default, for local clients like Claude Desktop, Kiro, Cursor) and optional HTTP (`MCP_TRANSPORT=http`) for hosted deployments.
@@ -182,10 +182,11 @@ EC2 uses a custom config transform (`lib/ec2.js`) that converts agent-friendly f
 
 ### Partition support
 
-The server supports three AWS partitions:
+The server supports the following AWS partitions:
 - `aws` — standard commercial regions
 - `aws-iso` — US ISO East/West
 - `aws-iso-b` — US ISOB East
+- `aws-eusc` (Experimental) AWS European Sovereign Cloud
 
 ### Export to calculator.aws
 
@@ -274,7 +275,7 @@ The catalog (`catalog/services/*.json`) is a set of curated per-service entries.
 
 | Status | Count | Meaning |
 |---|---|---|
-| `verified` | 16 | Reverified end-to-end: a fresh save from `minimalConfig` renders non-zero cost in calculator.aws |
+| `verified` | 18 | Reverified end-to-end: a fresh save from `minimalConfig` renders non-zero cost in calculator.aws |
 | `partial` | 1 | Authored but not fully verified |
 | **Total entries** | **17** | Out of ~436 services in the manifest |
 
@@ -299,7 +300,7 @@ The cost-oracle sweep saves a fresh estimate from each verified entry's `minimal
 
 The 1.2.0 catalog content was audited along three independent axes before release.
 
-**Cost-rendering correctness (deterministic).** The `validate-catalog:cost` sweep saves each of the 16 verified entries' `minimalConfig` and confirms a non-zero rendered cost via the DOM oracle. Result: **16/16 entries render priced cost** (e.g. Lambda $699.80/mo, RDS PostgreSQL $175.75/mo, EC2 $70.08/mo).
+**Cost-rendering correctness (deterministic).** The `validate-catalog:cost` sweep saves each of the verified entries' `minimalConfig` and confirms a non-zero rendered cost via the DOM oracle. Result: **entries render priced cost** (e.g. Lambda $699.80/mo, RDS PostgreSQL $175.75/mo, EC2 $70.08/mo).
 
 **Trap content audit (manifest cross-check + LLM cold-eye).** Each `traps[]` claim was checked against the live manifest data and, where applicable, the saved blob of the corresponding `verifiedEstimateId`. Result across the 60 shipped traps: **0 hallucinated claims**. Every trap was then classified by the type of utility it provides to a runtime agent — falling roughly into:
 
@@ -321,7 +322,7 @@ The trap audit and earns-place data are summarized here for transparency; the de
 - With the default `memory` store, in-flight estimates don't persist across restarts. Use `ESTIMATES_STORE=dynamodb` for stateless or multi-replica deployments.
 - No local cost calculation — pricing is computed by AWS when viewing the shareable link. Press **Update estimate** in the calculator UI to reflect the latest pricing.
 - Only `https://calculator.aws/` is supported.
-- Catalog coverage is partial (16 verified entries against ~436 manifest services). Uncatalogued services still benefit from the lint and trace events; they just don't get the magnitude-calibration role the catalog plays.
+- Catalog coverage is partial (verified entries against ~436 manifest services). Uncatalogued services still benefit from the lint and trace events; they just don't get the magnitude-calibration role the catalog plays.
 
 ## Security
 

package/catalog/services/aWSDataTransfer.json

@@ -0,0 +1,26 @@
+{
+  "$schema": "../schema.json",
+  "serviceCode": "aWSDataTransfer",
+  "displayName": "AWS Data Transfer",
+  "templateId": "awsDatatransfer",
+  "status": "verified",
+  "lastVerifiedAt": "2026-06-17",
+  "verifiedEstimateId": "0000000000000000000000000000000000000000",
+  "traps": [
+    "The dataTransfer field is a composite dataTransferV2 widget. Its value must be an array of transfer entries, each with entryType, value, unit, and a region field. Valid entryTypes: INBOUND, OUTBOUND, INTRA_REGION.",
+    "Unit must be \"tb_month\" or \"gb_month\".",
+    "OUTBOUND entries require a \"toRegion\" field — use \"External\" for internet or \"other\" for other AWS regions. INBOUND entries require a \"fromRegion\" field with the same options. INTRA_REGION requires neither.",
+    "All three entryTypes (INBOUND, OUTBOUND, INTRA_REGION) must be present in the array even if their value is \"0\"."
+  ],
+  "minimalConfig": {
+    "region": "us-east-1",
+    "description": "Data Transfer",
+    "dataTransfer": {
+      "value": [
+        { "entryType": "INBOUND", "value": "0", "unit": "tb_month", "fromRegion": "External" },
+        { "entryType": "OUTBOUND", "value": "1", "unit": "tb_month", "toRegion": "External" },
+        { "entryType": "INTRA_REGION", "value": "1", "unit": "tb_month" }
+      ]
+    }
+  }
+}

package/catalog/services/amazonElasticBlockStore.json

@@ -0,0 +1,27 @@
+{
+  "$schema": "../schema.json",
+  "serviceCode": "amazonElasticBlockStore",
+  "displayName": "Amazon Elastic Block Store (EBS)",
+  "templateId": "elasticBlockStore",
+  "status": "partial",
+  "lastVerifiedAt": "2026-06-17",
+  "verifiedEstimateId": "23290262d80f4d88c38df1ce90524f8d129db99f",
+  "traps": [
+    "gp3Throughput is a throughput-type field. The correct format is {\"value\": \"<number>\", \"unit\": \"mbps\"}. Do NOT use the options id from get_service_fields — the unit is always \"mbps\".",
+    "gp3Throughput minimum is 125 MBps (included in baseline), maximum is 2000 MBps. Only throughput above 125 MBps incurs additional cost.",
+    "gp3Iops minimum is 3000 (included in baseline), maximum is 80000. Only IOPS above 3000 incur additional cost.",
+    "storageType must be one of the full option IDs from the dropdown (e.g. \"Storage General Purpose gp3 GB Mo\"), not shorthand like \"gp3\".",
+    "snapshotFrequency uses numeric string IDs (e.g. \"0\" for no snapshots, \"30\" for daily, \"729\" for hourly) — not human-readable labels."
+  ],
+  "minimalConfig": {
+    "region": "us-east-1",
+    "description": "EBS gp3 Volume",
+    "numberOfInstances": "1",
+    "durationOfInstanceRuns": {"value": "730", "unit": "hours"},
+    "storageType": "Storage General Purpose gp3 GB Mo",
+    "storageAmount": {"value": "30", "unit": "gb|NA"},
+    "gp3Iops": "3000",
+    "gp3Throughput": {"value": "125", "unit": "mbps"},
+    "snapshotFrequency": "0"
+  }
+}

package/catalog/services/ec2Enhancement.json

@@ -14,7 +14,7 @@
     },
     {
       "field": "pricingStrategy",
-      "hint": "Pricing model. Accepts shorthand strings (ondemand, reserved, convertible, instanceSavings, computeSavings, spot) or a full object {model, term, upfrontPayment}. Valid term: '1yr' or '3yr'. Valid upfrontPayment: 'None', 'Partial', 'All'. EstimateBuilder normalizes via lib/ec2.js.",
+      "hint": "Pricing model. Accepts shorthand strings for simple cases OR a full object for committed pricing.\n\nShorthand (On-Demand/Spot only): \"ondemand\", \"spot\"\n\nFull object (required for any committed/discounted pricing):\n- EC2 Instance Savings Plans: {\"model\":\"instanceSavings\",\"term\":\"1 Year\",\"upfrontPayment\":\"None\"}\n- Compute Savings Plans: {\"model\":\"computeSavings\",\"term\":\"1 Year\",\"upfrontPayment\":\"None\"}\n- Standard Reserved Instances (dedicated tenancy only): {\"model\":\"standard\",\"term\":\"1 Year\",\"upfrontPayment\":\"None\"}\n- Convertible Reserved Instances (dedicated tenancy only): {\"model\":\"convertible\",\"term\":\"1 Year\",\"upfrontPayment\":\"None\"}\n\nValid term values: \"1 Year\", \"3 Year\" (exact case, full words)\nValid upfrontPayment values: \"None\", \"Partial\", \"All\" (exact case)\n\nCRITICAL: Do NOT use shorthand \"reserved\" or \"instanceSavings\" for committed pricing — these may silently fall back to On-Demand or produce $0 costs. Always use the full object format for any non-OnDemand, non-Spot pricing. EstimateBuilder normalizes via lib/ec2.js.",
       "enum": [
         "ondemand",
         "reserved",
@@ -28,12 +28,17 @@
   ],
   "traps": [
     "Use serviceCode 'ec2Enhancement' with templateId 'template'. The legacy (eC2Next, quickEstimate) format saves cleanly but renders Read-only — the calculator cannot rehydrate it. EstimateBuilder forces this transformation automatically; do not bypass it.",
-    "Reserved Instances (standard, convertible) are HIDDEN under shared tenancy. For shared, 'reserved' silently maps to 'instance-savings' and 'convertible' to 'compute-savings'. To use real RIs, set tenancy to 'dedicated' or 'host'.",
+    "Reserved Instances (standard, convertible) are HIDDEN under shared tenancy. For shared tenancy with committed pricing, ALWAYS use the full object format: {\"model\":\"instanceSavings\",\"term\":\"1 Year\",\"upfrontPayment\":\"None\"} or {\"model\":\"computeSavings\",\"term\":\"1 Year\",\"upfrontPayment\":\"None\"}. The shorthand \"reserved\" and \"instanceSavings\" strings are unreliable and may produce On-Demand pricing or $0 costs. Real Standard/Convertible RIs require tenancy:\"dedicated\" or \"host\".",
     "pricingStrategy term values are exact-case strings: '1 Year', '3 Year' — full words, capitalized. Lowercase variants silently produce wrong pricing.",
     "pricingStrategy upfrontPayment values: 'None', 'Partial', 'All'. EstimateBuilder accepts shorthand 'No' and converts to 'None'.",
     "The calculator silently demands tenancy, workload, workloadSelection, dataTransferForEC2, detailedMonitoringCheckbox, and ec2AdvancedPricingMetrics — even though the PCT does not mark them validations.required. EstimateBuilder injects all of these via lib/ec2.js#transformConfig.",
-    "utilization is HIDDEN inside the pricingStrategy component and does NOT appear in get_service_fields' field list. Production case 2026-06-03 (estimate 7898fb2d65a09e...): user asked for 80% utilization, agent saw no utilization field, gave up and told the user to 'apply a 0.8x multiplier' manually. To set utilization, pass top-level utilization: 'N' (string, 1–100); EstimateBuilder routes it into pricingStrategy.value.utilizationValue.",
-    "workload is the INSTANCE COUNT — use it for the user's quantity. For 'two instances' set workload: 2 (one entry) or save two entries with workload: 1 each. Either is fine. Do NOT save workload: 1 for 'two instances' and stash the '2' only in description (the saved estimate prices for one instance and the user reads two). Do NOT compensate for utilization with workload (e.g. workload: 0.8 to fake 80% utilization) — the total cost may match but the saved estimate structurally lies about how many instances are running. Use the explicit utilization field instead."
+    "utilization is HIDDEN inside the pricingStrategy component and does NOT appear in get_service_fields' field list. To set utilization, pass top-level utilization: 'N' (string, 1–100); EstimateBuilder routes it into pricingStrategy.value.utilizationValue.",
+    "workload is the INSTANCE COUNT — use it for the user's quantity. For 'two instances' set workload: 2 (one entry) or save two entries with workload: 1 each. Either is fine. Do NOT save workload: 1 for 'two instances' and stash the '2' only in description (the saved estimate prices for one instance and the user reads two). Do NOT compensate for utilization with workload (e.g. workload: 0.8 to fake 80% utilization) — the total cost may match but the saved estimate structurally lies about how many instances are running. Use the explicit utilization field instead.",
+    "The dataTransferForEC2 field is a composite widget. Its value must be an array of transfer entries, each with entryType, value, unit, and a region field. Valid entryTypes: INBOUND, OUTBOUND, INTRA_REGION.",
+    "Unit must be \"tb_month\" or \"gb_month\".",
+    "OUTBOUND entries require a \"toRegion\" field — use \"External\" for internet or \"other\" for other AWS regions. INBOUND entries require a \"fromRegion\" field with the same options. INTRA_REGION requires neither.",
+    "All three entryTypes (INBOUND, OUTBOUND, INTRA_REGION) must be present in the array even if their value is \"0\"."
+
   ],
   "minimalConfig": {
     "region": "us-east-1",
@@ -46,8 +51,8 @@
   "defaultFields": {
     "dataTransferForEC2": {
       "value": [
-        { "entryType": "INBOUND", "value": "", "unit": "tb_month", "fromRegion": "" },
-        { "entryType": "OUTBOUND", "value": "", "unit": "tb_month", "toRegion": "" },
+        { "entryType": "INBOUND", "value": "", "unit": "tb_month", "fromRegion": "External" },
+        { "entryType": "OUTBOUND", "value": "", "unit": "tb_month", "toRegion": "External" },
         { "entryType": "INTRA_REGION", "value": "", "unit": "tb_month" }
       ]
     }