Agent Chef

Get ingredients on hand

get_ingredients

Read-only

Retrieve pantry ingredients and leftovers the household already has so shopping lists exclude them; staples stay on hand unless marked out, and expired leftovers drop off automatically.

Instructions

What the household already has, so the shopping list can skip it. Staples (staple: true) are always on hand unless marked out; leftovers carry expires_at and drop off on their own.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.1Oct 3, 2026

addedOutput schema / properties / items / items / properties / expires_at

Added value: +{
+  "description": "Leftover: skipped until this time, then dropped",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / items / items / properties / out

Added value: +{
+  "description": "A staple the household ran out of; it is on the shopping list until an order restocks it",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / items / items / properties / staple

Added value: +{
+  "description": "Always on hand; skipped on every shopping list unless out",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

First observedv0.1.0Sep 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine domain behavior beyond them: staples are always on hand unless marked out, and leftovers carry expires_at and drop off automatically — non-obvious data semantics that affect how results should be interpreted.

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 compact sentences, zero filler, and the core purpose is front-loaded before the qualifying details about staples and leftovers. Every clause carries information.

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?

With no parameters, an existing output schema, and annotations covering the safety profile, the only thing the description needs to supply is domain semantics — and it does so for staples and expiring leftovers. Nothing required for a correct call is missing.

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?

The tool takes zero parameters, which is the baseline-4 case. The description correctly spends no words on arguments and instead explains the returned data semantics.

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?

The description names the resource concretely ('What the household already has') and its role ('so the shopping list can skip it'), so an agent understands it returns the household's on-hand ingredients. It does not explicitly contrast itself with the write-side sibling update_ingredients, but the read intent is unmistakable.

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 only implied via the purpose clause 'so the shopping list can skip it' — the agent can infer this is a read used when assembling a shopping list. No explicit when-to-use, prerequisites, or named alternatives (e.g. update_ingredients) are given.

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