Skip to main content
Glama
Tandoor Recipes MCP

Tandoor Recipes MCP

List inventory entries

list_inventory_entries
Read-onlyIdempotent

List inventory entries to see what is on hand and where; filter by location or food, include zero-quantity entries, and page through results.

Instructions

List inventory entries (what is on hand, where). Optional: location_id, food_id, include_empty (entries with amount 0 or less are hidden unless true), page, page_size.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_inventory_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
formatNoslim (default) returns a compact shape. full returns the raw Tandoor object.
food_idNoOnly entries for this food ID, from list_foods.
page_sizeNoResults per page.
location_idNoOnly entries at this location ID, from list_inventory_locations.
include_emptyNoInclude entries with amount 0 or less. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.4.4
    • addedInput schema / properties / food_id / description
      Added value: +"Only entries for this food ID, from list_foods."
    • addedInput schema / properties / include_empty / description
      Added value: +"Include entries with amount 0 or less. Default false."
    • addedInput schema / properties / location_id / description
      Added value: +"Only entries at this location ID, from list_inventory_locations."
    • addedInput schema / properties / page / description
      Added value: +"Page number, starting at 1."
    • addedInput schema / properties / page_size / description
      Added value: +"Results per page."
  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.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds a genuinely non-obvious behavior: entries with amount 0 or less are hidden unless include_empty is true, which an agent could otherwise misread as an empty result set. It stops short of describing ordering or pagination totals.

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?

Two short sentences, with the identity of the resource front-loaded before the options. The second sentence is a compressed parameter roll-call that duplicates the schema but is compact enough not to be wasteful.

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?

Six optional parameters, no required arguments, full schema coverage, and no output schema to compensate for. The description covers what the tool returns conceptually ('what is on hand, where'), the default filtering rule, and the available narrowing filters — everything needed to call it correctly.

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 every parameter including the slim/full format enum is already documented, which sets the baseline at 3. The description's list of optional parameters largely restates the schema, and it omits the format parameter entirely, adding no meaning beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List inventory entries') and adds a semantic gloss — 'what is on hand, where' — that tells an agent this is current stock, not a shopping list or a location catalog. It does not explicitly contrast with the nearby siblings list_shopping_entries or list_inventory_locations, so sibling differentiation is left implicit.

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 by the enumeration of optional filters (location_id, food_id, include_empty, pagination), which suggests 'use this to browse or filter stock on hand.' There is no explicit when-to-use versus alternatives, no exclusions, and no statement that the related list_* tools are the source of the filter IDs — that mapping lives only in the schema.

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