Skip to main content
Glama
Pantrist-dev

Pantrist

Official

reduce_pantry_amount

Adjust pantry item stock by a specified amount. Automatically add to shopping list when stock falls below the minimum threshold.

Instructions

Change the stock of an existing pantry item by a delta. Mutates state and returns the updated ArticleDto. If autoRestock is true and the new amount lands at or below the item's minimumAmount, the item is also added to the shopping list in the same call. Use add_pantry_item to create a new pantry entry; use update_pantry_item for metadata (name / unit / category) — this tool only touches stock.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYesItem uuid (from `list_pantry_items[].uuid`). Item must already exist in the pantry — this tool does not create.
amountChangeYesDelta added to the current `amount` — negative consumes stock, positive restocks. Despite the tool name, positive values work for restocking too.
autoRestockNoIf true and the resulting amount drops to or below the item's `minimumAmount` (with `manageMinimumAmount` enabled), the item is also added to the shopping list in the same call. Defaults to false so reads stay quiet.
listIdNoList UUID — call `list_lists` to discover one. Optional only in stdio mode (falls back to the PANTRIST_LIST_ID env var); required explicitly in HTTP mode.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses mutation, return of updated DTO, autoRestock side effect, and that positive values work for restocking. Lacks permission or reversibility details but covers key behavioral traits well.

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?

Two sentences, front-loaded with purpose, then details and sibling differentiation. No wasted words, efficient and clear structure.

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?

No output schema but description states return type. Parameters fully explained, sibling context provided, side effects documented. Complete for a tool of this complexity.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds extra context: amountChange clarifies positive works for restocking, autoRestock explains condition and default, listId distinguishes stdio vs HTTP modes. Adds meaningful value beyond schema.

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 clearly states it changes stock by a delta, distinguishes from 'add_pantry_item' (create) and 'update_pantry_item' (metadata), and specifies the exact resource and action.

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?

Explicitly tells when to use alternatives (add_pantry_item for creation, update_pantry_item for metadata) and explains the autoRestock side effect, providing clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantrist-dev/pantrist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server