Skip to main content
Glama

BusCalc — Business & Trade Calculations

Dated fuel and currency references

buscalc_market_price_references
Read-only

Fetch EIA monthly state/sector electricity or natural-gas averages, seasonal reported US residential/wholesale propane/heating-oil prices, weekly gasoline/diesel references, or ECB daily rates. Not real-time utility tariffs. Electricity converted from cents/kWh to USD/kWh; gas USD/Mcf; liquid fuels USD/US gallon. Returns observation date, retrieval time, source, units and cadence; fuel also includes publication time. Not tick prices, bank execution rates or local retail offers. Old/unavailable data fails explicitly. Reference lookups are counted separately from successful math. 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": {
        "kind": "fuel"
      }
    },
    "name": "buscalc_market_price_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNo
inputsYes
modelVersionNo

Output Schema

NameRequiredDescriptionDefault
kindYes
notesYes
sourceYes
cadenceYes
referenceYes
calculatorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / inputs / properties / kind / enum
      Previous value: -[
      -  "fuel",
      -  "fx"
      -]New value: +[
      +  "fuel",
      +  "fx",
      +  "electricity",
      +  "natural-gas",
      +  "propane",
      +  "heating-oil"
      +]
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered; the description still adds real value beyond that by disclosing unit normalization (cents/kWh to USD/kWh, USD/Mcf, USD/US gallon), the returned metadata fields (observation date, retrieval time, source, units, cadence, plus publication time for fuel), explicit failure on stale/unavailable data, and that reference lookups are counted separately from successful math. That last detail is a billing-side behavior an agent could not infer from the annotations. Nothing here contradicts the readOnly/openWorld hints.

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 first two sentences are well front-loaded and dense with genuinely useful scope and unit information. The back half degrades into meta-instructions about MCP argument shaping ("Put tool fields inside inputs," "Do not pass the REST calculator field inside MCP arguments") that read as transport boilerplate rather than tool semantics and dilute the signal. Several of those trailing sentences restate the schema rather than earning their place.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the key returned fields and the unit conventions, which is helpful. Coverage of error behavior and lookup accounting rounds out what an agent needs to call this correctly. The only real gap is the undocumented `units` object, which leaves one of three parameters opaque.

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 description coverage is 0%, so the description must carry the parameter burden, and it partially does: the enumerated data families map onto the `kind` enum values (electricity, natural-gas, propane, heating-oil, fuel, fx) and the unit conventions clarify what each returns. But the `units` parameter is an empty object with additionalProperties=false whose purpose is never explained, and `modelVersion` is only mentioned via "Supply units or modelVersion only when listed in inputSchema," which restates the schema rather than explaining it.

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?

Uses a specific verb ("Fetch") and enumerates the exact resource families: EIA monthly state/sector electricity and natural-gas averages, seasonal US residential/wholesale propane and heating-oil prices, weekly gasoline/diesel references, and ECB daily rates. It also carves out scope with "Not real-time utility tariffs" and "Not tick prices, bank execution rates or local retail offers," which separates it from market-data or utility-tariff tools. It stops short of naming the obvious sibling (buscalc_reference_price_calculations), so sibling differentiation is by exclusion rather than by routing.

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?

The negative scoping (not real-time tariffs, not tick prices, not bank execution rates, not local retail offers) gives an agent implicit guidance on when this tool is inappropriate, and "Old/unavailable data fails explicitly" sets an expectation about failure modes. However, there is no positive statement of when to pick this over buscalc_reference_price_calculations or buscalc_map_fuel_stops, and the trailing instruction block ("Put tool fields inside inputs") is argument-shape advice rather than when-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources