Skip to main content
Glama
Tandoor Recipes MCP

Tandoor Recipes MCP

Add inventory item

add_inventory_item

Add food to inventory by providing food ID, unit ID, amount, and location ID; optionally set expiry date, sub-location, note, or code.

Instructions

Add food to inventory. Required: food_id, unit_id, amount (> 0), location_id. Optional: expires (YYYY-MM-DD), sub_location, note, code. Always creates a new entry, even when the same food already has an entry at that location.

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": {
      "food_id": "<food_id>",
      "unit_id": "<unit_id>",
      "amount": "<amount>",
      "location_id": "<location_id>"
    },
    "name": "add_inventory_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoShort label, up to 16 characters. Default: the entry ID in hex.
noteNoFree-text note, up to 256 characters.
amountYesAmount, in unit_id.
formatNoslim (default) returns a compact shape. full returns the raw Tandoor object.
expiresNoExpiry date, YYYY-MM-DD.
food_idYesFood ID, from list_foods.
unit_idYesUnit ID, from list_units.
location_idYesInventory location ID, from list_inventory_locations.
sub_locationNoSpot within the location, such as a shelf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv3.4.4
    • addedInput schema / properties / amount / description
      Added value: +"Amount, in unit_id."
    • addedInput schema / properties / code / description
      Added value: +"Short label, up to 16 characters. Default: the entry ID in hex."
    • addedInput schema / properties / expires / description
      Added value: +"Expiry date, YYYY-MM-DD."
    • addedInput schema / properties / food_id / description
      Added value: +"Food ID, from list_foods."
    • addedInput schema / properties / location_id / description
      Added value: +"Inventory location ID, from list_inventory_locations."
    • addedInput schema / properties / note / description
      Added value: +"Free-text note, up to 256 characters."
    • addedInput schema / properties / sub_location / description
      Added value: +"Spot within the location, such as a shelf."
    • addedInput schema / properties / unit_id / description
      Added value: +"Unit ID, from list_units."
  2. Changed1 schema field changedv3.4.1
    • addedInput schema / properties / format / description
      Added value: +"slim (default) returns a compact shape. full returns the raw Tandoor object."
  3. First observedv3.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, but the description adds real context the annotations cannot convey: repeated calls create duplicate entries rather than updating in place. That explains the practical consequence of non-idempotency. It still omits failure behavior for unknown food_id/unit_id and what the call returns.

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?

Three short sentences, front-loaded with the action and then the non-obvious creation semantics. The required/optional enumeration slightly duplicates the schema's required array, but it is compact and improves scanability. Nothing is padded or vague.

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 9-parameter creation tool with full schema coverage, no output schema, and safety annotations, the description covers the essentials: what it creates, which fields are mandatory, and the duplicate-entry behavior. Gaps are minor — the format parameter (slim/full) and the shape of the returned entry are not mentioned, though the schema documents the former.

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 every parameter including enum values, date pattern, and code/note length limits. The description's required/optional list and the amount > 0 and YYYY-MM-DD notes restate schema content rather than adding interpretation. Baseline 3 is appropriate; it adds scannability but no new meaning.

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 opens with a specific verb and resource ('Add food to inventory') and immediately clarifies the creation semantics: 'Always creates a new entry, even when the same food already has an entry at that location.' That single clause separates it from move_inventory_item and consume_inventory_item, which act on existing entries, so an agent can route correctly without reading schemas.

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?

Usage is implied rather than stated: the reader infers this is the tool for putting new stock into a location, and the 'always creates a new entry' clause implicitly warns against expecting merge/upsert behavior. There is no explicit when-not guidance, no mention of using move_inventory_item to relocate existing stock, and no stated prerequisites (e.g., resolving food_id and unit_id first).

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