BusCalc — Business & Trade Calculations

FluxNeed

buscalc_fluxneed

Read-onlyIdempotent

Compare independent resource actions for one demand scenario and budget. Use consistent units. Mobility and environmental availability are fractions from 0 to 1. No live data is fetched. 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": {
        "unit": "crew-hours",
        "budget": 5000,
        "demand": 100,
        "actions": [
          {
            "cost": 2000,
            "name": "Reassign a crew",
            "capacity": 50,
            "mobility": 0.8,
            "environment": 0.5,
            "feasibility": "confirmed"
          }
        ],
        "available": 30,
        "referenceEvidence": {
          "rows": [
            {
              "unit": "USD/kWh",
              "label": "Electricity rate",
              "value": 0.16
            }
          ],
          "title": "Illustrative electricity cost",
          "source": "/electricity-cost-calculator/",
          "calculatedAt": "2026-11-09T00:00:00Z"
        }
      }
    },
    "name": "buscalc_fluxneed"
  }
}

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.

AddedNov 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, closed-world operation. The description reinforces that no live data is fetched and adds unit and field-placement constraints, but it does not explain the comparison behavior, how scoring changes results, or what happens with invalid action combinations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description contains several short, partially redundant or confusing sentences, including 'Supply units or modelVersion only when listed in inputSchema' and 'Do not pass the REST calculator field inside MCP arguments.' Some guidance earns its place, while other sentences are vague or duplicate schema constraints.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with many nested optional objects, an enum, and no top-level schema descriptions. The description covers the basic shape and a few constraints, but it does not adequately explain the input model, the role of scoring or forecastBenefit, or the evidence fields, leaving the agent reliant on the schema example and annotations.

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 saying to use consistent units, that mobility and environmental availability are fractions from 0 to 1, and that fields belong inside inputs. With 0% schema description coverage, however, it leaves most nested fields such as demand, available, budget, actions, feasibility, and scoring unexplained.

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: compare independent resource actions for one demand scenario and budget. This is clear enough for an agent to understand the tool's core function, though it does not explicitly distinguish it from related siblings such as buscalc_foreneed or buscalc_need_velocity.

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 gives procedural guidance such as using consistent units, placing fields inside inputs, and not passing a REST calculator field. However, it does not say when to use this tool versus alternatives, nor does it provide explicit when-not conditions.

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?