Skip to main content
Glama

Utility Matrix

by io.github.helphub369
OverviewDiscussionsAdmin

On-Call Burden Calculator

on-call-burden-calculator
Read-onlyIdempotent

Use when a user asks about on-call load or burnout risk. Uses team size, rotation length, and hourly rate exactly as the browser calculator does.

Input Schema

NameRequiredDescriptionDefault
team_sizeYesteam size used by this deterministic tool.
hourly_rateYeshourly rate used by the calculation; monetary values are in USD unless stated otherwise.
rotation_weeksYesrotation weeks used by this deterministic tool.

Output Schema

NameRequiredDescriptionDefault
next_stepYes
annual_costYes
output_tierYes
monthly_costYes
signal_valueYes
next_step_urlYes
remaining_pctYes
why_follow_upYes
interpretationYes
pct_working_timeYes
affiliate_contextNo
computation_basisYes
hours_per_engineerYes
shifts_per_engineerYes
total_hours_per_monthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / properties / engineer_count
      Removed value: -{
-  "minimum": 1,
-  "type": "number"
-}
    • removedInput schema / properties / hourly_cost
      Removed value: -{
-  "minimum": 0,
-  "type": "number"
-}
    • addedInput schema / properties / hourly_rate
      Added value: +{
+  "description": "hourly rate used by the calculation; monetary values are in USD unless stated otherwise.",
+  "examples": [
+    1
+  ],
+  "minimum": 0,
+  "type": "number"
+}
    • removedInput schema / properties / hours_per_shift
      Removed value: -{
-  "minimum": 1,
-  "type": "number"
-}
    • addedInput schema / properties / rotation_weeks
      Added value: +{
+  "description": "rotation weeks used by this deterministic tool.",
+  "examples": [
+    1
+  ],
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • removedInput schema / properties / shifts_per_month
      Removed value: -{
-  "minimum": 1,
-  "type": "number"
-}
    • addedInput schema / properties / team_size
      Added value: +{
+  "description": "team size used by this deterministic tool.",
+  "examples": [
+    1
+  ],
+  "minimum": 1,
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "engineer_count",
-  "shifts_per_month",
-  "hours_per_shift",
-  "hourly_cost"
-]New value: +[
+  "team_size",
+  "rotation_weeks",
+  "hourly_rate"
+]
  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"
+    },
+    "hours_per_engineer": {
+      "type": "number"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "monthly_cost": {
+      "type": "number"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "next_step_url": {
+      "type": "string"
+    },
+    "output_tier": {
+      "type": "string"
+    },
+    "pct_working_time": {
+      "type": "number"
+    },
+    "remaining_pct": {
+      "type": "number"
+    },
+    "shifts_per_engineer": {
+      "type": "number"
+    },
+    "signal_value": {
+      "type": "number"
+    },
+    "total_hours_per_month": {
+      "type": "number"
+    },
+    "why_follow_up": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "annual_cost",
+    "computation_basis",
+    "hours_per_engineer",
+    "interpretation",
+    "monthly_cost",
+    "next_step",
+    "next_step_url",
+    "output_tier",
+    "pct_working_time",
+    "remaining_pct",
+    "shifts_per_engineer",
+    "signal_value",
+    "total_hours_per_month",
+    "why_follow_up"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and determinism profile is largely covered. The description adds that it is deterministic and mirrors 'the browser calculator exactly,' a modest but real addition about result parity; it says nothing about units of the output or precision beyond what the schema carries.

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?

Two sentences, no filler, with the usage trigger front-loaded before the input summary. Appropriately sized for a simple deterministic calculator.

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 and annotations carry the safety/determinism profile, so the description need not explain return values. For a low-complexity, three-required-parameter calculator, the entry is sufficient, though the vague 'burnout risk' framing is never grounded in what the computed number actually represents.

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 all three parameters are documented structurally, and the description merely names the same inputs (team size, rotation length, hourly rate). It adds no syntax, formatting, or edge-case guidance beyond the schema's minimum/exclusiveMinimum constraints.

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 and title together convey that the tool computes an on-call burden figure from team size, rotation length, and hourly rate. The purpose is clear, but it never explicitly distinguishes itself from the closely related alert-fatigue-calculator or burnout-adjacent siblings, so the agent must infer the boundary.

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 when a user asks about on-call load or burnout risk" gives a clear triggering condition. It lacks any exclusion or alternative guidance, which matters given 30+ sibling calculators including alert-fatigue-calculator that could plausibly be confused with this one.

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