Skip to main content
Glama
Sign In

Utility Matrix

by io.github.helphub369
OverviewDiscussionsAdmin

Kubernetes Cluster Capacity Calculator

cluster-capacity-calculator
Read-onlyIdempotent

Use this when a user asks for Kubernetes cluster capacity. Uses the same node vCPU, node memory, node count, system reserve, and target utilization model as the browser calculator.

Input Schema

NameRequiredDescriptionDefault
node_vcpuYesnode vcpu used by this deterministic tool.
node_countYesnode count used by this deterministic tool.
node_mem_gbYesnode mem in gigabytes.
system_reserve_pctNosystem reserve expressed as a percentage.
target_utilization_pctNotarget utilization expressed as a percentage.

Output Schema

NameRequiredDescriptionDefault
raw_vcpuYes
next_stepYes
node_countYes
output_tierYes
usable_vcpuYes
signal_valueYes
next_step_urlYes
raw_memory_gbYes
remaining_pctYes
why_follow_upYes
interpretationYes
usable_memory_gbYes
affiliate_contextNo
computation_basisYes
allocatable_factorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed29 schema fields changed
    • addedInput schema / properties / node_count
      Added value: +{
+  "description": "node count used by this deterministic tool.",
+  "examples": [
+    1
+  ],
+  "minimum": 1,
+  "type": "number"
+}
    • removedInput schema / properties / node_cpu
      Removed value: -{
-  "type": "number"
-}
    • addedInput schema / properties / node_mem_gb
      Added value: +{
+  "description": "node mem in gigabytes.",
+  "examples": [
+    0.001
+  ],
+  "minimum": 0.001,
+  "type": "number"
+}
    • removedInput schema / properties / node_memory_gb
      Removed value: -{
-  "type": "number"
-}
    • addedInput schema / properties / node_vcpu
      Added value: +{
+  "description": "node vcpu used by this deterministic tool.",
+  "examples": [
+    0.001
+  ],
+  "minimum": 0.001,
+  "type": "number"
+}
    • removedInput schema / properties / nodes
      Removed value: -{
-  "type": "number"
-}
    • removedInput schema / properties / pod_cpu_m
      Removed value: -{
-  "type": "number"
-}
    • removedInput schema / properties / pod_memory_mb
      Removed value: -{
-  "type": "number"
-}
    • removedInput schema / properties / pods
      Removed value: -{
-  "type": "number"
-}
    • addedInput schema / properties / system_reserve_pct
      Added value: +{
+  "description": "system reserve expressed as a percentage.",
+  "examples": [
+    1
+  ],
+  "maximum": 99.999,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / target_utilization_pct
      Added value: +{
+  "description": "target utilization expressed as a percentage.",
+  "examples": [
+    0.001
+  ],
+  "maximum": 100,
+  "minimum": 0.001,
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "nodes",
-  "node_cpu",
-  "node_memory_gb"
-]New value: +[
+  "node_vcpu",
+  "node_mem_gb",
+  "node_count"
+]
    • removedOutput schema / properties / allocatable_cpu_cores
      Removed value: -{
-  "type": "number"
-}
    • addedOutput schema / properties / allocatable_factor
      Added value: +{
+  "type": "number"
+}
    • removedOutput schema / properties / allocatable_memory_gb
      Removed value: -{
-  "type": "number"
-}
    • addedOutput schema / properties / computation_basis
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / cpu_utilization_pct
      Removed value: -{
-  "type": "number"
-}
    • removedOutput schema / properties / memory_utilization_pct
      Removed value: -{
-  "type": "number"
-}
    • addedOutput schema / properties / node_count
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / output_tier
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / pressure_level
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / raw_memory_gb
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / raw_vcpu
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / remaining_pct
      Added value: +{
+  "type": "number"
+}
    • removedOutput schema / properties / severity
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / signal_value
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / usable_memory_gb
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / usable_vcpu
      Added value: +{
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "allocatable_cpu_cores",
-  "allocatable_memory_gb",
-  "cpu_utilization_pct",
-  "interpretation",
-  "memory_utilization_pct",
-  "next_step",
-  "next_step_url",
-  "pressure_level",
-  "severity",
-  "why_follow_up"
-]New value: +[
+  "allocatable_factor",
+  "computation_basis",
+  "interpretation",
+  "next_step",
+  "next_step_url",
+  "node_count",
+  "output_tier",
+  "raw_memory_gb",
+  "raw_vcpu",
+  "remaining_pct",
+  "signal_value",
+  "usable_memory_gb",
+  "usable_vcpu",
+  "why_follow_up"
+]
  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"
+    },
+    "allocatable_cpu_cores": {
+      "type": "number"
+    },
+    "allocatable_memory_gb": {
+      "type": "number"
+    },
+    "cpu_utilization_pct": {
+      "type": "number"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "memory_utilization_pct": {
+      "type": "number"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "next_step_url": {
+      "type": "string"
+    },
+    "pressure_level": {
+      "type": "string"
+    },
+    "severity": {
+      "type": "string"
+    },
+    "why_follow_up": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "allocatable_cpu_cores",
+    "allocatable_memory_gb",
+    "cpu_utilization_pct",
+    "interpretation",
+    "memory_utilization_pct",
+    "next_step",
+    "next_step_url",
+    "pressure_level",
+    "severity",
+    "why_follow_up"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

A3.8/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 safety profile is fully covered structurally. The description adds only that the tool is deterministic and reuses the browser calculator's model, which is mild context but not a disclosure the agent couldn't infer.

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?

Two sentences, zero filler, with the trigger condition front-loaded before the model-fidelity note. Nothing could be removed without losing information.

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?

With an output schema present, return values need not be explained, and the annotations cover safety. What remains thin is guidance on parameter interaction and defaults, but for a deterministic calculator with fully documented inputs, the description is adequate.

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 five parameters, and the description merely echoes their names. It adds no units, defaults, or interaction rules (e.g., how system_reserve_pct and target_utilization_pct combine) beyond what the schema states, making the baseline 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 names the specific resource (Kubernetes cluster capacity) and the trigger condition, so an agent can tell this apart from generic siblings like rightsizing-calculator or total-cost-of-ownership-calculator. It never uses an explicit verb like 'calculates', relying on the tool name for that, but the intent is unambiguous.

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?

'Use this when a user asks for Kubernetes cluster capacity' gives a clear, specific activation context. It stops short of naming alternatives or stating when not to use it (e.g., versus rightsizing or node-count planning tools), so it lands at clear-context-without-exclusions.

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