BusCalc — Business & Trade Calculations

Precious metal calculations

buscalc_precious_metal_calculations

Read-onlyIdempotent

Calculate contained precious metal value, scrap payout, bullion premium, investment gain/loss, resale break-even or gold–silver ratio using explicit supplied USD prices. Optional price snapshots preserve source/time but are not independently authenticated. No live price is fetched by this tool. 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": {
        "method": "precious-metals-value",
        "figures": {
          "spot": 3000,
          "metal": "XAU",
          "purity": 100,
          "weight": 31.1034768,
          "weightUnit": "g"
        }
      }
    },
    "name": "buscalc_precious_metal_calculations"
  }
}

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": {
+      "figures": {
+        "metal": "XAU",
+        "purity": 100,
+        "spot": 3000,
+        "weight": 31.1034768,
+        "weightUnit": "g"
+      },
+      "method": "precious-metals-value"
+    }
+  }
+]

AddedNov 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: prices are caller-supplied USD only, and priceSnapshots are provenance metadata that is 'not independently authenticated'. That caveat is valuable and not derivable from the schema or annotations.

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 core capability and the no-live-price constraint are front-loaded in the first two sentences. The trailing instructions about wrapping fields in 'inputs' and not passing the REST calculator field are useful but read as boilerplate and could be tightened.

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?

For a six-variant oneOf tool with nested figures objects, the description covers the mode list, the price-source constraint, the snapshot caveat, and argument nesting. An output schema exists so return values need not be described, and the remaining gap is per-method field expectations, which the schema itself supplies.

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?

Top-level schema coverage is reported at 0%, so the description must carry meaning for the wrapper parameters, and it does partially: fields belong inside 'inputs', and 'units'/'modelVersion' should only be supplied when listed. It does not explain the method enum values or the per-method figure requirements, leaving the agent to read the oneOf branches.

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?

The description names a specific verb plus resource and enumerates all six supported calculation modes (contained value, scrap payout, bullion premium, gain/loss, resale break-even, gold–silver ratio), which maps directly onto the six oneOf variants in the schema. It also explicitly disclaims live pricing, which separates it from a quotes-style sibling.

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?

It states the operating condition clearly: calculations run on explicit supplied USD prices and 'No live price is fetched by this tool', which implicitly routes price-lookup needs elsewhere. It does not name the alternative tool, so the agent must infer that a quotes sibling exists rather than being told to use it.

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?