Skip to main content
Glama

Read supplies

inventory_list
Read-onlyIdempotent

Lists household supplies with quantities, units, thresholds, categories, and 30-day usage, flagging low stock. Use it to get item IDs for updates, consumption, and removal, and to check before adding.

Instructions

Lists all household supply items (toilet paper, detergent and similar) of the flat with quantity, unit, threshold, category and decrementCount30d (times the stock was reduced in the last 30 days). An item is low on stock when quantity <= threshold. Read-only. Call it first to get the item ids that inventory_update, inventory_consume and inventory_remove need, and to check for an existing item before inventory_add. Not for the shopping list; use shopping_list for that.

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": "inventory_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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally; the description still adds real value by defining derived semantics the agent cannot get elsewhere (low stock when quantity <= threshold, decrementCount30d meaning stock reductions in the last 30 days) and the upstream-dependency role. It stops short of describing ordering, pagination or empty-result behavior, and for a list tool returning many items pagination is the one meaningful gap. Credit is capped because the most decision-relevant behavioral facts (read-only, idempotent, non-destructive) come from annotations, not the text.

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?

Front-loaded with the resource and returned fields, then the low-stock rule, then dependencies, then the exclusion. Every sentence carries distinct information with no restatement of the name or title.

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 exists, yet the description effectively supplies one by naming the returned fields and their meanings, plus the derived low-stock predicate. Combined with annotations and full schema coverage on the single optional parameter, an agent has everything needed to call this correctly.

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%: the single wgCode parameter is fully documented in-schema, including the pattern, where the code comes from (wg_list) and the omission rule for single-flat accounts. The description adds no parameter detail beyond referring to "the flat," so this is the baseline case where the schema carries the load.

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?

Names a specific verb and resource ("Lists all household supply items") and enumerates exactly what comes back: quantity, unit, threshold, category and decrementCount30d. It explicitly rules out the adjacent resource with "Not for the shopping list; use shopping_list," so the agent can separate it from both the shopping tool and the inventory mutation siblings without opening a 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 concrete ordering guidance other tools don't state: call this first to obtain the item ids that inventory_update, inventory_consume and inventory_remove require, and to check for an existing item before inventory_add. It also names the exclusion case (shopping_list). This is exactly the when/when-not/alternatives pattern.

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