Skip to main content
Glama

Add a supply item

inventory_add

Create a new supply item for a shared flat when a product is not tracked yet; starting stock at or below its threshold automatically adds it to the shopping list.

Instructions

Creates a new supply item in the flat. Use it only for a product that is not tracked yet; to change stock of an existing item use inventory_consume or inventory_update. Item names are unique per flat, ignoring case and surrounding spaces; a taken name fails with 409 inventory_item_duplicate. If the starting quantity is already <= threshold (which the defaults give), the item is put on the shopping list automatically. Returns the created item.

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

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name of the product, for example "Toilet paper". Must be new in the flat.
unitNoUnit of measure for quantity and threshold. Defaults to piece.piece
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
categoryNoCategory used to group the item. Defaults to other.other
quantityNoCurrent stock in the chosen unit. Defaults to 0.
thresholdNoLow-stock limit in the chosen unit: at or below this quantity the item counts as low and goes on the shopping list. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / category / description
      Added value: +"Category used to group the item. Defaults to other."
    • addedInput schema / properties / name / description
      Added value: +"Display name of the product, for example \"Toilet paper\". Must be new in the flat."
    • addedInput schema / properties / quantity / description
      Added value: +"Current stock in the chosen unit. Defaults to 0."
    • addedInput schema / properties / threshold / description
      Added value: +"Low-stock limit in the chosen unit: at or below this quantity the item counts as low and goes on the shopping list. Defaults to 1."
    • addedInput schema / properties / unit / description
      Added value: +"Unit of measure for quantity and threshold. Defaults to piece."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the uniqueness rule, the specific 409 inventory_item_duplicate failure, and the automatic shopping-list side effect when quantity is at or below threshold. It also states that the created item is returned, which matters because annotations already establish this is a non-idempotent write.

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 front-loaded with purpose and alternatives, then failure behavior, then side effects, and closes with the return value. Every sentence carries useful information and none of it repeats the title or name alone.

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?

For a six-parameter creation tool with no output schema, the description covers selection, uniqueness failure, automatic side effect, and return value. Nothing essential for calling it correctly appears to be missing.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all six parameters, including defaults, enums, and the name uniqueness constraint. The description reinforces the quantity/threshold relationship but adds little parameter-level meaning beyond what the schema provides.

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 states a specific verb and resource (creates a new supply item) and immediately distinguishes it from inventory_consume and inventory_update, which are for existing items. An agent can select this tool 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 Guidelines5/5

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

It gives an explicit when-to-use rule (only for a product not tracked yet) and names the alternatives to use when changing stock of an existing item. No ambiguity remains about the intended selection.

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