Simple Inventory Management

add_inventory_unit

Adds a stock line to an inventory item. Provide inventory item id, name, optional identifier (serial, lot code, or other label), quantity (default 1), and status (InStock, Ordered, Outbound, Damaged). Use quantity greater than 1 for fungible groups (e.g. 5 of the same lot). An item can track at most 500 stock lines. Returns the created line.

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": {
      "inventoryItemId": "<inventoryItemId>",
      "name": "<name>"
    },
    "name": "add_inventory_unit"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`status`	No	InStock
`quantity`	No
`identifier`	No
`inventoryItemId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose some behavior: defaults for quantity and status, the 500-stock-line cap per item, and that the created line is returned. It does not cover permission requirements, whether identifier must be unique, or what happens on failure, which are material gaps for an unannotated mutation tool.

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?

The purpose is front-loaded in the first sentence, followed by compact parameter guidance and a limit note. It repeats the schema's quantity default of 1, a minor redundancy, but no sentence is filler and the total length is appropriate.

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 5-parameter mutation tool with no annotations and no output schema, the description covers the parameters, the per-item cap, and the return value, which is most of what an agent needs. Coverage of error conditions and identifier uniqueness would make it complete.

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% and the schema declares no enums, so the description does all the work: it explains identifier as "serial, lot code, or other label" and enumerates the allowed status values (InStock, Ordered, Outbound, Damaged), plus clarifies quantity semantics. This adds substantial meaning beyond the bare property types.

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?

"Adds a stock line to an inventory item" names a specific verb (adds) and resource (stock line), and the phrase "to an inventory item" implicitly separates it from create_new_inventory_item, which creates the item itself. An agent can pick this tool over its siblings without opening the schema.

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

Usage Guidelines4/5

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

It gives concrete usage guidance for quantity ("use quantity greater than 1 for fungible groups (e.g. 5 of the same lot)") and the required inventoryItemId makes clear this applies only to existing items. It lacks an explicit when-not or a named alternative such as create_new_inventory_item for new items, which keeps it below a 5.

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

All Simple Inventory Management 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?