Inventory-domain MCP tools for Magebit_Mcp (multi-source inventory: sources, stocks, source items, salable quantity)
Three tools with complete JSON schemas, clear descriptions (120-180 chars), and proper parameter validation. Naming follows verb_noun pattern (inventory.bulk.*). All parameters typed and constrained (minLength, maxItems, exclusiveMinimum). Strong error handling via ServiceErrorMessage flattening MSI validation errors. Gaps: no output schemas documented, no tool annotations (destructiveHint/readOnlyHint), no per-item error reporting for bulk operations, descriptions lack dependency hints or recovery guidance.
Move a specific quantity of each SKU from one source to another — a stock rebalance rather than a full move. The origin keeps whatever is left over and stays assigned. Use `inventory.bulk.transfer` to move entire balances instead.
Assign every listed SKU to every listed source in one operation, creating source items with zero quantity where they do not exist. Use this to stand up a new warehouse; set quantities afterwards with `inventory.source_item.set`. Affects up to 1000 SKUs per call.
Remove every listed SKU from every listed source in one operation. DESTRUCTIVE: the source items are deleted along with their quantities, salable quantity drops on every website the affected stocks serve, and there is no undo. To move stock rather than destroy it, use `inventory.bulk.transfer`.
No output schemas documented. LLMs cannot infer response structure, field names, or success indicators. Bulk operations should return per-item success/failure counts.
Missing tool annotations. inventory.bulk.source_unassign is DESTRUCTIVE but lacks destructiveHint. inventory.bulk.source_assign is WRITE but lacks readOnlyHint=false. Agents cannot distinguish safe from risky operations.
Descriptions lack recovery guidance. 'Use inventory.bulk.transfer instead' references a tool not in this server. No hints on how to handle partial failures or validation errors.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 69 | 2026-07-28+ | v2 |
Bulk operations accept up to 1000 SKUs but return no per-item error reporting. If 1 SKU fails validation, the entire batch fails with no indication which SKU caused the problem.
No idempotency guarantees documented. Agents retry on ambiguous failures, bulk operations should declare idempotency or support a dry-run mode to prevent duplicate assignments.