CargoMind MCP Server

Overview Schema Source Related Servers Discussions Admin

check_inventory

Query stock levels by SKU and warehouse, flag low-stock items, and see open purchase orders to guide replenishment decisions.

Instructions

Check stock levels per SKU and warehouse, including low-stock flags and any open purchase order.

Args:
    sku: SKU ID ("SKU-107") or product name fragment ("insulin", "gloves"). Empty = all SKUs.
    warehouse_id: Warehouse ID ("WH-BLR"), code ("BLR") or city ("Bangalore"). Empty = all warehouses.
    low_stock_only: If true, only lines at or below their reorder point.

Returns:
    {"status": "ok", "count", "low_stock_count", "items": [{sku, name, warehouse_id, qty_on_hand,
    reorder_point, shortfall, low_stock, open_po, ...}]}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sku`	No
`warehouse_id`	No
`low_stock_only`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full load. It discloses that this is a read-style lookup and describes the shape and semantics of the returned item fields (shortfall, low_stock, open_po), but says nothing about permissions, scoping restrictions, or behavior when the result set is large. An output schema exists, so reciting return fields adds less value than it appears.

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?

Front-loaded purpose sentence followed by structured Args/Returns blocks, so the agent can parse it quickly. The Returns block restates information already carried by the output schema, which is mild redundancy, but nothing is bloated or buried.

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?

For a three-optional-parameter read tool with an output schema available, the description covers invocation semantics and result contents adequately. It omits anything about permission requirements, rate/cost behavior, or result-size limits when all SKUs and warehouses are requested, which are the remaining gaps.

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

Parameters5/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 compensate, and it does: each of the three parameters is explained with concrete value formats ('SKU-107', 'WH-BLR'/'BLR'/'Bangalore'), a fragment-matching convention for product names, and the meaning of empty/default values. This is exactly what the schema fails to provide.

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 ('Check stock levels per SKU and warehouse') and enumerates the payload of the result (low-stock flags, open purchase order), which clearly separates it from write-side siblings like create_reorder. It does not explicitly name a sibling it replaces, so it stops short of the top band.

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 description gives invocation context for each parameter (empty string means all SKUs / all warehouses) and defines low_stock_only operationally, which is useful. However, it never says when to prefer this tool over alternatives such as get_kpis or create_reorder, and there are no exclusions or prerequisites stated.

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

Deploy Server