Skip to main content
Glama

finops_unit_economics

Read-onlyIdempotent

Computes cost per unit, splits fixed versus variable costs, and identifies the volume where marginal cost crosses a target using caller-supplied costs without guessing provider prices.

Instructions

Compute cost per unit (request, customer, transaction), fixed versus variable split and the volume at which the marginal cost crosses a target. Caller supplies costs; no provider prices are guessed.

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": {
      "period": "<period>",
      "units": "<units>"
    },
    "name": "finops_unit_economics"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsYes
periodYes
currencyNoUSD
fixedCostsNo
variableCostsNo
targetCostPerPrimaryUnitNo

Output Schema

NameRequiredDescriptionDefault
kindNo
periodNo
totalsNo
perUnitNo
readingNo
sourcesNo
currencyNo
validatedNo
limitationNo
limitationsNo
breakEvenVolumeForTargetNo
marginalCostPerPrimaryUnitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.5.0
    • removedInput schema / properties / fixedCosts / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / units / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / variableCosts / items / additionalProperties
      Removed value: -false
    • changedInput schema / required
      Previous value: -[
      -  "period",
      -  "currency",
      -  "fixedCosts",
      -  "variableCosts",
      -  "units"
      -]New value: +[
      +  "period",
      +  "units"
      +]
    • addedOutput schema / properties / limitation
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / sources
      Added value: +{
      +  "type": "array"
      +}
    • addedOutput schema / properties / validated
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  2. First observedv0.4.1

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the read-only, idempotent, closed-world annotations, the description discloses data provenance and an important limitation: costs come from the caller and provider prices are not invented. Formula details and edge-case behavior remain unstated, but the provenance disclosure adds meaningful behavioral context.

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 compact sentences front-load the calculations and then state the input-provenance constraint. There is no filler, and although the first sentence is dense, each clause contributes useful selection or invocation information.

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 annotations and output schema reduce the descriptive burden, and the main purpose and data limitation are covered. For a six-parameter calculator with no schema descriptions, the missing primary-unit rule, target-crossing formula, and period/currency expectations still leave material invocation and interpretation ambiguities.

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?

With 0% schema description coverage, the unit examples and fixed/variable/target terminology partially compensate by explaining the main inputs conceptually. However, it does not define period or currency semantics, whether cost amounts are totals for that period, or which units entry is the primary unit referenced by targetCostPerPrimaryUnit.

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 uses a specific verb and identifies three concrete outputs: cost per unit, fixed-versus-variable split, and a target-crossing volume. The unit examples further clarify scope, but there is no explicit differentiation from the sibling cost_model tool.

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?

Requiring caller-supplied costs and disclaiming provider-price guessing establishes a useful boundary: use this for calculations on known cost data, not for price discovery. It does not explicitly state when to choose cost_model or another sibling for broader modeling or pricing needs.

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