Skip to main content
Glama

BRAINIAC Inventory Intelligence

Report inventory optimization

inventory-intelligence_optimization-report

Combine stockout risk, reorder points, safety stock, excess, slow-moving stock, and demand forecasts from supplied data. No purchase order is created. Price $0.12 USDC. POST /api/v1/inventory-intelligence/optimization-report. 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_optimization-report"
  }
}

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

B3.2/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 supply real operational facts the schema cannot convey: the operation is read-only analysis with no purchase order side effect, it costs $0.12 USDC, and unpaid calls return 402 without executing. What it omits is equally material — the shape of the returned report, error behavior for insufficient input data, and any input minimums across the 16 parameters.

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 with the capability statement front-loaded, followed by scope, price, endpoint, and payment behavior — no filler. The endpoint path is arguably redundant operational detail, but it earns its place for a paid HTTP-style tool.

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

Completeness3/5

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

For a 16-parameter, nested-input tool with no annotations, no output schema, and 0% schema coverage, the description covers purpose, cost, payment failure mode, and non-mutation but leaves the input model and return value entirely unexplained. An agent knows what the tool is for and what it costs, but not how to populate the arguments or what it will get back.

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 (including a nested file object and four record arrays), so the description needs to compensate and does not — no parameter is mentioned, explained, or prioritized. It never clarifies that inputs can be supplied as csv/json/text/file or as structured arrays, nor what asOf, forecastDays, slowDays, or serviceLevelZ control. Only the metric names hint at what the outputs mean, and parameter names alone must be guessed at.

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 opens with a specific verb and resource: 'Combine stockout risk, reorder points, safety stock, excess, slow-moving stock, and demand forecasts from supplied data.' Listing all six sibling analyses together makes clear this is the aggregating roll-up tool rather than another single-metric calculator. It stops short of explicitly naming the siblings it supersedes, so differentiation is inferable but not stated.

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?

Usage context is implied by 'Combine ... from supplied data' — reach for this when you want every inventory metric at once — and 'No purchase order is created' sets a scope boundary. However, there is no explicit when-to-use/when-not guidance versus the individual calculators, and no prerequisites (e.g. minimum required inputs) are stated.

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