Skip to main content
Glama

BRAINIAC Inventory Intelligence

Normalize inventory data

inventory-intelligence_data-normalize

Copy supplied products, sales, supplier lead times, and purchases into a consistent inventory packet. Missing lead times and prices are not invented. Price $0.04 USDC. POST /api/v1/inventory-intelligence/data-normalize. 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_data-normalize"
  }
}

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 at all, the description must carry the behavioral load, and it does deliver real value: the $0.04 USDC price, the 402-does-not-run failure mode, and the important guarantee that missing lead times and prices are not invented. What it omits is what the returned packet contains, how the four input channels are merged or prioritized, and whether the operation is idempotent.

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 tight sentences, front-loaded with the core operation before the data-integrity caveat and the commercial/transport details. Nothing is padded, though the endpoint string and price could arguably be consolidated.

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 tool with nested objects, no output schema, and no annotations, the description is thin. An agent can form a rough intent but cannot confidently populate the many tuning parameters or anticipate the shape of the normalized packet it will receive 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, so the description is the only source of meaning, and it covers only the broad input channels (products, sales, lead times, purchases). Parameters such as asOf, slowDays, slowUnits, reviewDays, historyDays, forecastDays, serviceLevelZ, excessDaysCover, and the csv/json/text/file alternatives are never mentioned, leaving most of the schema opaque.

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 names a specific verb-and-resource pair: it copies products, sales, supplier lead times, and purchases into a consistent inventory packet. That distinguishes it from the analytics siblings (forecast, reorder-point, safety-stock) which consume rather than normalize data. It stops just short of explicitly framing this as the ingestion step that precedes those tools.

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 statement of when to choose this tool over the analytics siblings, nor any precondition such as 'call this first before demand-forecast'. The only usage-adjacent information is the payment and endpoint mechanics, which govern how to call it, not when.

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