Skip to main content
Glama
Sign In

Utility Matrix

by io.github.helphub369
OverviewDiscussionsAdmin

Total Cost of Ownership Calculator

total-cost-of-ownership-calculator
Read-onlyIdempotent

Use when a user asks about TCO or multi-year SaaS cost.

Input Schema

NameRequiredDescriptionDefault
oneTimeFeesNooneTimeFees used by this deterministic tool.
numPaidSeatsYesnumPaidSeats used by this deterministic tool.
contractLengthNocontractLength used by this deterministic tool.
perUserMonthlyFeeNoperUserMonthlyFee used by this deterministic tool.
adminHoursPerMonthNoadminHoursPerMonth used by this deterministic tool.
expectedActiveUsersYesexpectedActiveUsers used by this deterministic tool.
internalHourlyCost105NointernalHourlyCost105 used by this deterministic tool.
baseMonthlySubscriptionNobaseMonthlySubscription used by this deterministic tool.

Output Schema

NameRequiredDescriptionDefault
next_stepYes
do_savingsYes
output_tierYes
monthly_costYes
signal_valueYes
next_step_urlYes
why_follow_upYes
contract_totalYes
interpretationYes
seat_waste_pctYes
contract_monthsYes
shelfware_seatsYes
overpaying_flagsYes
year1_admin_costYes
year1_total_costYes
affiliate_contextNo
computation_basisYes
year1_vendor_costYes
seat_waste_cost_yrYes
cost_per_user_monthlyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / properties / adminHoursPerMonth / description
      Added value: +"adminHoursPerMonth used by this deterministic tool."
    • addedInput schema / properties / adminHoursPerMonth / examples
      Added value: +[
+  1
+]
    • addedInput schema / properties / baseMonthlySubscription / description
      Added value: +"baseMonthlySubscription used by this deterministic tool."
    • addedInput schema / properties / baseMonthlySubscription / examples
      Added value: +[
+  1
+]
    • addedInput schema / properties / contractLength / description
      Added value: +"contractLength used by this deterministic tool."
    • addedInput schema / properties / contractLength / examples
      Added value: +[
+  1
+]
    • addedInput schema / properties / expectedActiveUsers / description
      Added value: +"expectedActiveUsers used by this deterministic tool."
    • addedInput schema / properties / expectedActiveUsers / examples
      Added value: +[
+  1
+]
    • addedInput schema / properties / internalHourlyCost105 / description
      Added value: +"internalHourlyCost105 used by this deterministic tool."
    • addedInput schema / properties / internalHourlyCost105 / examples
      Added value: +[
+  1
+]
    • addedInput schema / properties / numPaidSeats / description
      Added value: +"numPaidSeats used by this deterministic tool."
    • addedInput schema / properties / numPaidSeats / examples
      Added value: +[
+  1
+]
    • addedInput schema / properties / oneTimeFees / description
      Added value: +"oneTimeFees used by this deterministic tool."
    • addedInput schema / properties / oneTimeFees / examples
      Added value: +[
+  1
+]
    • addedInput schema / properties / perUserMonthlyFee / description
      Added value: +"perUserMonthlyFee used by this deterministic tool."
    • addedInput schema / properties / perUserMonthlyFee / examples
      Added value: +[
+  1
+]
  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"
+    },
+    "computation_basis": {
+      "type": "string"
+    },
+    "contract_months": {
+      "type": "number"
+    },
+    "contract_total": {
+      "type": "number"
+    },
+    "cost_per_user_monthly": {
+      "type": "number"
+    },
+    "do_savings": {
+      "type": "number"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "monthly_cost": {
+      "type": "number"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "next_step_url": {
+      "type": "string"
+    },
+    "output_tier": {
+      "type": "string"
+    },
+    "overpaying_flags": {
+      "type": "number"
+    },
+    "seat_waste_cost_yr": {
+      "type": "number"
+    },
+    "seat_waste_pct": {
+      "type": "number"
+    },
+    "shelfware_seats": {
+      "type": "number"
+    },
+    "signal_value": {
+      "type": "number"
+    },
+    "why_follow_up": {
+      "type": "string"
+    },
+    "year1_admin_cost": {
+      "type": "number"
+    },
+    "year1_total_cost": {
+      "type": "number"
+    },
+    "year1_vendor_cost": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "computation_basis",
+    "contract_months",
+    "contract_total",
+    "cost_per_user_monthly",
+    "do_savings",
+    "interpretation",
+    "monthly_cost",
+    "next_step",
+    "next_step_url",
+    "output_tier",
+    "overpaying_flags",
+    "seat_waste_cost_yr",
+    "seat_waste_pct",
+    "shelfware_seats",
+    "signal_value",
+    "why_follow_up",
+    "year1_admin_cost",
+    "year1_total_cost",
+    "year1_vendor_cost"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

B3.2/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 full safety profile of this side-effect-free computation is covered by structured data. The description adds no behavioral context of its own (no mention of determinism, formula scope, or units), but for a pure read-only calculator with complete annotations there is little left to disclose. No contradiction with annotations.

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?

A single front-loaded sentence with zero filler; the trigger is stated immediately. It is efficient but so terse that the brevity tips into under-specification rather than genuine conciseness, which caps it below 5.

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 not be explained, and rich annotations cover the safety profile of this read-only computation. The remaining gap is param semantics and sibling routing for an 8-parameter financial model, which the one-line description does not address.

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 nominally 100%, so the baseline is 3 per the rubric. The description contributes nothing about any of the 8 parameters, and the schema descriptions are generic placeholders, so no extra meaning is added. Baseline 3 is the correct landing spot.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the domain (TCO, multi-year SaaS cost) and the name itself signals a calculator, so an agent can infer the resource being computed. However, it never states what the tool actually computes or returns, reading as a trigger phrase rather than a purpose statement. It only partially separates this tool from the many other cost siblings (ec2-cost-calculator, pipeline-cost-calculator, software-purchase-risk-calculator).

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?

"Use when a user asks about TCO or multi-year SaaS cost" gives an explicit trigger condition, which is real usage guidance. It offers no when-not, no prerequisites, and no routing against the crowded set of cost-oriented siblings, so an agent facing an ambiguous cost question still has to guess. This is implied-to-partial guidance rather than a complete selection rule.

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
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources