BusCalc — Business & Trade Calculations

Bounded ranges and uncertainty propagation

buscalc_uncertainty

Read-onlyIdempotent

Propagate2..8 hard intervals through sum/difference/product/quotient, or combine1..8 uncorrelated standard-uncertainty terms using entered derivatives. Interval arithmetic expands endpoints outward; statistical coverage factors do not establish confidence levels. Returns a calculation receipt with inputs, results, assumptions, validation checks and source. The receipt is unsigned, not independent certification. No private data, external lookup or arbitrary code execution. Put tool fields inside inputs. Supply units or modelVersion only when listed in inputSchema. Follow its required fields and exact choices. Do not pass the REST calculator field inside MCP arguments.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputs": {
        "mode": "interval",
        "ranges": [
          {
            "low": 2,
            "high": 3
          },
          {
            "low": 4,
            "high": 5
          }
        ],
        "operation": "product"
      }
    },
    "name": "buscalc_uncertainty"
  }
}

Input Schema

Name	Required	Description	Default
`units`	No
`inputs`	Yes
`modelVersion`	No

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

addedInput schema / examples

Added value: +[
+  {
+    "inputs": {
+      "mode": "interval",
+      "operation": "product",
+      "ranges": [
+        {
+          "high": 3,
+          "low": 2
+        },
+        {
+          "high": 5,
+          "low": 4
+        }
+      ]
+    }
+  }
+]

AddedNov 4, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: interval arithmetic expands endpoints outward, coverage factors do not imply confidence levels, the receipt includes assumptions and validation checks, and the receipt is unsigned and not independent certification. It also states that there is no private data use, external lookup, or arbitrary code execution, which is substantive behavioral context for a read-only calculator.

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?

The purpose is front-loaded in the first sentence, and the remaining sentences add operational caveats without excessive repetition. The paragraph is dense and mixes purpose, parameter routing, output caveats, and usage warnings, so a little more structure would help, but it is appropriately sized for a complex nested tool.

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?

Given the nested oneOf schema, annotations, and output schema, the description covers the main modes, arithmetic assumptions, output receipt, and safety boundaries. It does not explain every schema-level constraint such as the divisor excluding zero, but the schema carries those details and the description is broadly complete for correct invocation.

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?

The description adds some meaning beyond the schema by calling the ranges hard intervals, describing 2..8 interval operands, and describing 1..8 uncorrelated standard-uncertainty terms with entered derivatives. It still leaves gaps around the empty units object, modelVersion usage, and nested mode constraints, so it only partially compensates for the low reported schema description coverage.

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 states a specific verb and resource: propagate bounded intervals through four named operations, or combine uncorrelated standard-uncertainty terms using entered derivatives. This is much clearer than a generic calculator, but it does not explicitly distinguish itself from nearby siblings such as statistics, probability, or sensitivity tools.

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?

It implies when each mode applies by naming interval arithmetic versus linear independent propagation, and it warns not to use the REST calculator field. However, it gives no explicit when-to-use or when-not-to-use guidance against sibling tools, and it does not state conditions for choosing this over probability or statistics.

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

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

Need Help?