Skip to main content
Glama

Utility Matrix

by io.github.helphub369
OverviewDiscussionsAdmin

Terraform Plan Cost Estimator

terraform-plan-cost-estimator
Read-onlyIdempotent

Use when a user asks to estimate monthly cost of a Terraform plan.

Input Schema

NameRequiredDescriptionDefault
countYescount used by this deterministic tool.
instance_sizeNoinstance size used by this deterministic tool.
resource_typeYesresource type used by this deterministic tool.

Output Schema

NameRequiredDescriptionDefault
next_stepYes
annual_costYes
hourly_rateYes
output_tierYes
monthly_costYes
signal_valueYes
next_step_urlYes
resource_typeYes
why_follow_upYes
interpretationYes
resource_countYes
affiliate_contextNo
computation_basisYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / count / description
      Added value: +"count used by this deterministic tool."
    • addedInput schema / properties / count / examples
      Added value: +[
+  1
+]
    • addedInput schema / properties / instance_size / description
      Added value: +"instance size used by this deterministic tool."
    • addedInput schema / properties / instance_size / examples
      Added value: +[
+  "example"
+]
    • addedInput schema / properties / resource_type / description
      Added value: +"resource type used by this deterministic tool."
    • addedInput schema / properties / resource_type / examples
      Added value: +[
+  "example"
+]
  2. Changed1 schema field changed
    • 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"
+    },
+    "annual_cost": {
+      "type": "number"
+    },
+    "computation_basis": {
+      "type": "string"
+    },
+    "hourly_rate": {
+      "type": "number"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "monthly_cost": {
+      "type": "number"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "next_step_url": {
+      "type": "string"
+    },
+    "output_tier": {
+      "type": "string"
+    },
+    "resource_count": {
+      "type": "number"
+    },
+    "resource_type": {
+      "type": "string"
+    },
+    "signal_value": {
+      "type": "number"
+    },
+    "why_follow_up": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "annual_cost",
+    "computation_basis",
+    "hourly_rate",
+    "interpretation",
+    "monthly_cost",
+    "next_step",
+    "next_step_url",
+    "output_tier",
+    "resource_count",
+    "resource_type",
+    "signal_value",
+    "why_follow_up"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds no behavioral context beyond the usage trigger, such as determinism, limitations, or scope restrictions.

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 a single front-loaded sentence with no wasted words. It is appropriately sized for the amount of information it conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema and output schema are rich, and annotations cover safety traits, so the description need not explain return values. However, it does not clarify how a Terraform plan maps to the required resource_type, count, and instance_size inputs, nor does it differentiate from numerous sibling cost calculators.

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 three parameters. The description does not add any parameter-level meaning, making the baseline score of 3 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?

The description states a specific action and target: estimating monthly cost of a Terraform plan. It is clear what the tool does, though it does not explicitly differentiate itself from closely related cost estimators beyond the Terraform plan wording.

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?

It gives a clear trigger: use when a user asks to estimate monthly cost of a Terraform plan. It does not provide when-not-to-use guidance or name alternative sibling tools, but the intended context is explicit.

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

All Utility Matrix toolsInspect
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