Skip to main content
Glama

Read the shopping list

shopping_list
Read-onlyIdempotent

Retrieves a shared flat's shopping list, including open items and recent purchases with IDs and timestamps, so you can check duplicates, update bought status, or remove entries.

Instructions

Read the flat's shopping list: every open item (oldest first), followed by the most recently bought items (newest first, capped at about 1000). Each item has id, name, quantity, addedBy/addedByName, boughtBy, boughtAt (null while open) and updatedAt. Call it first to get the id (for shopping_set_bought and shopping_remove) and the updatedAt and boughtAt that shopping_set_bought requires, or to check for an open duplicate before shopping_add. For supplies stock instead of things to buy, use inventory_list.

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": "shopping_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this a safe idempotent read, and the description adds genuinely useful behavior beyond them: result ordering, an approximate result cap ('about 1000'), the per-item field set, and the fact that boughtAt is null while an item is open. The only softness is the vague cap wording, which leaves an agent unsure of the exact truncation boundary.

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?

Three tight sentences, front-loaded with what is returned before the usage guidance, and no filler. The middle sentence is dense with dependent clauses (id, updatedAt, boughtAt uses) and reads slightly run-on, but every clause carries operational 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?

There is no output schema, so the description carries the burden of describing return values, and it does so fully: ordering, cap, field names, and null semantics for boughtAt. Combined with the id/prerequisite guidance, an agent has everything needed to call this correctly and chain into the mutation siblings.

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 coverage is 100% and the single wgCode parameter is fully documented in the schema with its pattern and the multi-flat fallback. The description adds no additional meaning about the parameter beyond referencing 'the flat's shopping list', 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 (read the flat's shopping list) plus the exact contents and ordering: all open items oldest-first, then recent purchases newest-first capped at ~1000. It explicitly distinguishes itself from the sibling inventory_list (supplies stock vs. things to buy), so an agent can separate the two without opening either 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?

Names concrete downstream uses and prerequisites: get the id needed by shopping_set_bought and shopping_remove, get updatedAt and boughtAt required by shopping_set_bought, and check for an open duplicate before shopping_add. It also gives an explicit exclusion with an alternative ('For supplies stock ... use inventory_list'), so both when-to-use and when-not-to-use are covered.

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