Skip to main content
Glama

BRAINIAC Inventory Intelligence

Forecast inventory demand

inventory-intelligence_demand-forecast

Forecast units as averageDailyDemand × forecastDays from available dated sales only. Seasonality is not modeled and uncertainty is disclosed. Price $0.05 USDC. POST /api/v1/inventory-intelligence/demand-forecast. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inventory-intelligence_demand-forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
salesNo
productsNo
slowDaysNo
purchasesNo
slowUnitsNo
suppliersNo
reviewDaysNo
historyDaysNo
forecastDaysNo
serviceLevelZNo
excessDaysCoverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: the flat average-daily-demand formula, the explicit limitation that seasonality is not modeled, that uncertainty is disclosed, the $0.05 USDC charge, and that unpaid calls return 402 without running. What it omits is significant for a 16-parameter tool — it says nothing about what the supplier, purchase, slow-moving, or service-level inputs actually do, nor what the response contains.

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?

Four short sentences, front-loaded with the core formula before caveats, pricing, and the failure mode. Dense and mostly waste-free, though the raw endpoint path and the price sentence sit slightly apart from the operational content.

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?

For a tool with 16 undocumented parameters, nested objects, no annotations, and no output schema, the description covers only a fraction of what an agent needs to call it correctly. The agent cannot tell what most inputs are for or what the response shape will be, which is a substantial gap given the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 16 parameters, several of them nested objects (sales, products, purchases, suppliers), so the description must compensate and it largely does not. It only conveys meaning for forecastDays (via the formula) and implicitly for dated sales records; slowDays, slowUnits, excessDaysCover, serviceLevelZ, historyDays, asOf, and the file/csv/json/text alternatives are all 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?

States a specific verb and resource ('Forecast units') and even gives the computation ('averageDailyDemand × forecastDays from available dated sales only'), so the agent knows exactly what comes out. It does not name or distinguish itself from any sibling such as safety-stock-calculate or reorder-point-calculate, which is the only thing keeping it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of which sibling handles reorder points, safety stock, or excess detection. The only contextual rules given are payment-related (price, 402 behavior), which are prerequisites rather than selection 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