Skip to main content
Glama
Pantrist-dev

Pantrist

Official
by Pantrist-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_shopping_items

Retrieve all items on your shopping list by providing the list ID. Returns item details including name, amount, and category.

Instructions

List all items currently on the shopping list for listId. Read-only. Returns an array of ArticleDto objects (uuid, name, amount, unitId, categoryUuid, pantrySettings, …); empty array if the list is empty. For pantry items use list_pantry_items; to add a new shopping item use add_shopping_item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / listId / description
      Previous value: -"List UUID. Defaults to PANTRIST_LIST_ID if omitted."New value: +"List 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."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It declares read-only, describes the return type (array of ArticleDto objects) and the empty array edge case, and explains the listId parameter behavior in different modes (stdio vs HTTP). Missing details on auth or rate limits.

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 that are front-loaded: first sentence states purpose and read-only nature; second sentence provides sibling references and return type. Every sentence earns its place with no wasted words.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers purpose, usage, parameter details, return type, edge case (empty array), and sibling tool references. It is complete for its context.

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

Parameters5/5

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

Schema coverage is 100% with a description for listId. The description adds significant context: how to discover the list ID via 'list_lists', and the fallback behavior in stdio mode (env var) vs HTTP mode (required). This goes beyond the 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 uses a specific verb 'list' and resource 'shopping items' with a required 'listId'. It clearly distinguishes from siblings like 'list_pantry_items' and 'add_shopping_item'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description explicitly provides alternatives: for pantry items use 'list_pantry_items'; to add items use 'add_shopping_item'. It also indicates read-only behavior, but does not explicitly state when not to use the tool.

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

Deploy Server

Other Tools