QuailOS

update_inventory_product

Idempotent

Update a General Inventory product by productId or sku: name, SKU, ASIN, barcode, category, prices, manufactured flag and BOM (bomComponents replaces the whole BOM; hasBom:false clears it). Stock is changed only via adjust_inventory_stock. Supports confirm (false = dry-run preview).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "farmId": "<farmId>"
    },
    "name": "update_inventory_product"
  }
}

Input Schema

Name	Required	Description
`sku`	No	Current SKU of the product to update (or use productId)
`asin`	No	Amazon ASIN
`unit`	No	Unit of measure (e.g. each, pair, lb)
`farmId`	Yes	The unique farm ID
`hasBom`	No	True for manufactured items that have a BOM recipe
`newSku`	No	New SKU (must be unique in the farm)
`status`	No	Product status (default active)
`barcode`	No	Barcode / UPC
`confirm`	No	Set to true to commit, false for dry-run preview
`category`	No	Inventory category
`productId`	No	Inventory product ID (or use sku)
`costPerUnit`	No	Cost per unit
`productName`	No	Product name
`reorderPoint`	No	Reorder point
`sellingPrice`	No	Selling price
`bomComponents`	No	BOM lines (replaces the whole BOM when given). Components must already exist in this farm's inventory.
`shortDescription`	No	Short description

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A5/5.0

Behavior5/5

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

The description details specific behavioral logic beyond the schema, notably that 'bomComponents replaces the whole BOM' and 'hasBom:false clears it.' This is critical information regarding state mutation that a schema cannot convey alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loads the most important information: what it does, how it identifies the target, its exclusions, and its execution modes. Every part of the sentence adds necessary functional context.

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

Completeness5/5

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

The definition is highly complete. It addresses identification, the scope of changes, crucial interaction with other tools (stock), and important mutation rules (BOM replacement), leaving no ambiguity for a complex data update operation.

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?

Although the schema is complete (100%), the description adds significant value by clarifying identification (productId or sku), detailing the stateful logic of the BOM parameters, and defining the intent of the 'confirm' parameter as a dry-run/commit toggle.

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 explicitly states the tool updates General Inventory products. It provides critical differentiation by specifying that the update targets can be specified by 'productId or sku,' and it steers the user away from stock changes by referencing adjust_inventory_stock.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear boundaries on usage by stating 'Stock is changed only via adjust_inventory_stock,' which explicitly directs the agent to the correct sibling tool. It also guides usage by explaining the function of the 'confirm' parameter for dry-run previews.

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

All QuailOS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?