Skip to main content
Glama

BRAINIAC Inventory Intelligence

Detect excess inventory

inventory-intelligence_excess-detect

Flag SKUs whose days of cover from supplied on-hand and average daily demand exceed the disclosed excessDaysCover threshold. Price $0.04 USDC. POST /api/v1/inventory-intelligence/excess-detect. 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_excess-detect"
  }
}

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 add real behavioral value: it discloses the $0.04 USDC price, the POST route, and that unpaid calls return 402 and do not execute — material context an agent needs before calling. However, it says nothing about the response shape, whether the operation is read-only, or how the large set of optional inputs affects results.

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?

Three tight sentences, front-loaded with the core logic before pricing and transport details. Every sentence carries distinct information, though the endpoint path is arguably redundant with the name for an agent that never constructs URLs.

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 16-parameter, nested-object tool with zero schema descriptions, no annotations, and no output schema, the description is too thin. It explains the calculation but not how to supply inventory/sales data across the five alternative input formats, what happens when no parameters are supplied (all are optional), or what the flagged output contains.

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 nested products, sales, purchases, suppliers, and file objects. The description clarifies only three concepts (on-hand, average daily demand, excessDaysCover) and leaves the choice between csv/json/text/file inputs and the defaults for historyDays, forecastDays, serviceLevelZ, slowDays, and reviewDays completely undocumented.

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 ('Flag SKUs'), the exact computation ('days of cover from supplied on-hand and average daily demand'), and the decision criterion ('exceed the disclosed excessDaysCover threshold'). An agent can distinguish this from siblings such as slow-moving-stock-detect or reorder-point-calculate without opening any schema.

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?

The description never states when to choose this tool over the many sibling inventory calculations (slow-moving, stockout-risk, reorder-point, safety-stock). It explains payment mechanics and the endpoint, but no situational or exclusionary guidance is given.

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