topai-mcp-suite

Overview Schema Source Related Servers Discussions Admin

terracost_blast_evaluate

Read-onlyIdempotent

Evaluates Terraform plan JSON to calculate infrastructure blast radius, flag high-risk stateful resource destruction, and estimate monthly FinOps cost changes before apply.

Instructions

Evaluates Terraform plan JSON output to calculate infrastructure blast radius, identify high-risk stateful resource destructions (databases, storage buckets), and compute monthly FinOps cost delta estimations. Use when: Pre-apply CI/CD infrastructure reviews, FinOps budget validation, or assessing destruction risk before applying Terraform changes. Do not use when: Linting container configurations or evaluating test flakiness. Alternative: Use dockerlean_wasm_audit for container optimization, or flaky_quarantine_analyze for CI test stability. Execution: Runs locally in-memory (<10ms), read-only, idempotent, zero network calls, zero telemetry, air-gapped deterministic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "planJson": "<planJson>"
    },
    "name": "terracost_blast_evaluate"
  }
}

Input Schema

Name	Required	Description	Default
`planJson`	Yes	Valid JSON output generated from 'terraform show -json <planfile>'.
`licenseKey`	No	Optional TopAI Sovereign Pro offline license key (or set TOPAI_LICENSE_KEY env variable).

Output Schema

Name	Required	Description	Default
`report`	Yes	Detailed resource delta counts, stateful destruction alerts, and monthly cost delta.
`markdown`	Yes	Formatted Markdown summary suitable for CI PR comments.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.6Oct 22, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / licenseKey

Added value: +{
+  "description": "Optional TopAI Sovereign Pro offline license key (or set TOPAI_LICENSE_KEY env variable).",
+  "type": "string"
+}

changedInput schema / properties / planJson / description

Previous value: -"Terraform plan JSON content"New value: +"Valid JSON output generated from 'terraform show -json <planfile>'."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "markdown": {
+      "description": "Formatted Markdown summary suitable for CI PR comments.",
+      "type": "string"
+    },
+    "report": {
+      "description": "Detailed resource delta counts, stateful destruction alerts, and monthly cost delta.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "report",
+    "markdown"
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful execution context beyond that: local in-memory execution, under 10ms, zero network calls, zero telemetry, and air-gapped deterministic operation. It does not contradict annotations, though some of this partially restates the safety profile.

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?

The description is front-loaded with the core action and supported by clearly labeled usage, exclusion, alternative, and execution sections. Every sentence contributes useful routing or behavioral information without padding.

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?

An output schema exists, so return-value explanation is unnecessary. With annotations covering safety traits and the schema covering parameters, the description adds the important scope, usage, alternatives, and execution environment details needed to invoke the tool correctly.

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 both parameters are fully documented in the schema, including the required terraform show -json format and the optional license key. The description does not add parameter-specific syntax or meaning beyond what the schema already provides, so the baseline of 3 applies.

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 states specific actions and resources: evaluating Terraform plan JSON, calculating blast radius, identifying stateful resource destructions, and computing FinOps cost delta. It also explicitly names sibling tools for adjacent but different tasks, so an agent can distinguish it without opening schemas.

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 provides explicit 'Use when' examples (pre-apply CI/CD reviews, FinOps budget validation, destruction risk assessment) and 'Do not use when' exclusions (container linting, test flakiness). It also names alternative tools for those excluded cases, making routing decisions unambiguous.

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

Deploy Server