LastList

Stock the pantry

stock_pantry

Add items to the user's grocery pantry inventory in bulk, creating the pantry list if they don't have one. Use when the user is telling you what's in their kitchen ('here's what I keep stocked', 'I have flour, sugar, rice and canned tomatoes'), which is what makes match_recipes_to_inventory and recipe_needs useful. Does not touch the shopping list — use have_items when the point is that they no longer need to buy something. Duplicates are skipped.

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

Input Schema

Name	Required	Description	Default
`items`	Yes	Item names to stock, e.g. ['flour', 'sugar', 'canned tomatoes'].
`title`	No	Title for the pantry list if one has to be created. Defaults to 'Pantry'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write profile is known. The description adds value beyond that: it will create the pantry list if absent, duplicates are skipped (an idempotency-style guarantee), and it will not modify the shopping list. It stops short of saying how fuzzy matching works or what the response contains.

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 core action is front-loaded in the first clause, and each following sentence contributes either a trigger example, an exclusion, or a behavioral note. The quoted examples are slightly verbose but earn their place by disambiguating this tool from have_items.

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 2-parameter bulk write with no output schema, the description covers creation behavior, duplicate handling, and boundary with the shopping list. Only minor gaps remain, such as whether item names are normalized against a catalog and what the call returns.

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 explains both the items array and the title default. The description reinforces that items are stocked in bulk but adds no syntax or matching detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource (add items to the grocery pantry inventory), adds bulk scope, and discloses the side effect of creating the pantry list. It explicitly carves itself away from the shopping list and from have_items, so an agent can place it among 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 Guidelines5/5

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

Gives a concrete trigger with quoted user utterances ('here's what I keep stocked', 'I have flour, sugar, rice...'), names the downstream tools the data enables, and supplies an explicit exclusion routed to the correct alternative ('use have_items when...'). This is the full when/when-not/alternative triad.

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

All LastList 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?