BusCalc — Business & Trade Calculations

Recipe portion cost

buscalc_recipe_portion_cost

Read-onlyIdempotent

Find the ingredient cost of a batch and each sellable portion from package prices and quantities used. Use this tested BusCalc worksheet when the task matches its inputs and scope. Returns named results, units, formula, assumptions, method version and a source-page URL. No prices or omitted costs are looked up; no private projects or purchases are accessed.

Input Schema

Name	Required	Description
`units`	No
`inputs`	Yes
`modelVersion`	No	Optional expected method version; a mismatch is rejected.

Output Schema

Name	Required	Description	Default
`units`	No
`inputs`	Yes
`receipt`	Yes
`results`	Yes
`sourceURL`	Yes
`calculator`	Yes
`modelVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "calculator": {
+      "type": "string"
+    },
+    "inputs": {
+      "type": "object"
+    },
+    "modelVersion": {
+      "type": "string"
+    },
+    "receipt": {
+      "properties": {
+        "additionalResults": {
+          "type": "object"
+        },
+        "assumptions": {
+          "type": "string"
+        },
+        "calculator": {
+          "type": "string"
+        },
+        "checks": {
+          "items": {
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "status": {
+                "enum": [
+                  "passed"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "name",
+              "status"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "formula": {
+          "type": "string"
+        },
+        "inputs": {
+          "type": "object"
+        },
+        "integrity": {
+          "type": "string"
+        },
+        "methodVersion": {
+          "type": "string"
+        },
+        "replay": {
+          "type": "string"
+        },
+        "replayRequest": {
+          "type": "object"
+        },
+        "results": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "schemaVersion": {
+          "enum": [
+            "1.0.0"
+          ],
+          "type": "string"
+        },
+        "scope": {
+          "type": "string"
+        },
+        "sourceURL": {
+          "format": "uri",
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "calculated"
+          ],
+          "type": "string"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "units": {
+          "type": "object"
+        },
+        "warnings": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "schemaVersion",
+        "status",
+        "tool",
+        "calculator",
+        "methodVersion",
+        "sourceURL",
+        "formula",
+        "assumptions",
+        "inputs",
+        "units",
+        "results",
+        "replayRequest",
+        "additionalResults",
+        "checks",
+        "warnings",
+        "scope",
+        "integrity",
+        "replay"
+      ],
+      "type": "object"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "unit": {
+            "type": "string"
+          },
+          "value": {
+            "oneOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "string"
+              }
+            ]
+          }
+        },
+        "required": [
+          "label",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sourceURL": {
+      "format": "uri",
+      "type": "string"
+    },
+    "units": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "calculator",
+    "modelVersion",
+    "sourceURL",
+    "inputs",
+    "results",
+    "receipt"
+  ],
+  "type": "object"
+}

First observedNov 3, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower; the description still adds value by disclosing the return payload (named results, units, formula, assumptions, method version, source-page URL) and by stating explicitly that no prices or omitted costs are looked up — a meaningful limitation for a costing tool.

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?

Four short sentences, purpose front-loaded, then a usage cue, then return shape, then scope limits. No sentence repeats another and nothing is padded beyond the borderline-boilerplate 'tested BusCalc worksheet' clause.

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?

An output schema exists so return values need not be explained (the description explains them anyway), and annotations cover safety. But for a nested three-parameter tool with only 33% schema description coverage and a conditional required-field structure, the description should clarify the two recipeEntry modes — that gap keeps it at adequate rather than complete.

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 coverage is only 33%, so the description should carry more weight here. 'Package prices and quantities used' does gesture at the per-ingredient path, but it never explains the recipeEntry branch (ingredients vs. total/batchCost) or the modelVersion mismatch behavior, leaving the two mutually exclusive input modes to be inferred from the schema's allOf.

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

Purpose5/5

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

States a specific verb and dual output: 'Find the ingredient cost of a batch and each sellable portion from package prices and quantities used.' That is concrete enough to distinguish it from every sibling (loan payment, break-even, markup vs margin) without opening a schema.

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 this tested BusCalc worksheet when the task matches its inputs and scope' is essentially circular — it tells the agent to use it when it's applicable. The closing sentence does add real negatives (no price lookup, no private project/purchase access), which is genuine exclusion guidance, but no alternative tool or when-not-to-use condition is named.

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

All BusCalc — Business & Trade Calculations tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?