LastList

Add items to a list

add_items

Add one or more items to the user's shopping list (or a specific list by id). Items appear in the user's LastList app on its next sync. Writes are literal — if an item might already be on the list, call get_list first and bump its quantity or skip it rather than adding a duplicate. Ask the user before adding items they didn't explicitly request.

Quantities: qty is always the COUNT OF BASE UNITS, not the number of packages. For 'a dozen eggs' send qty 12 with packSize 12 and packLabel 'dozen'; for 'two 12-packs of soda' send qty 24, packSize 12, packLabel '12-pack'. For anything sold by weight or volume ('2 lbs of chicken') send qty 2 with unit 'lb' and soldBy 'WEIGHT'. Getting this right is what lets the app's pack stepper and consume_items track what the user actually has.

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

Input Schema

Name	Required	Description	Default
`items`	Yes	One or more items to add.
`listId`	No	Optional list id. Defaults to the user's current shopping list.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that writes are literal, items appear after the next app sync, duplicate risk exists, and user confirmation is required for unrequested items. These are meaningful behavioral traits for a mutation tool with destructiveHint=false.

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?

The description is front-loaded with the core action and duplicate-safety workflow, then dedicates the second paragraph to the most error-prone parameter semantics. Every sentence contributes useful operational context.

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?

For a mutation tool with no output schema and complex nested item parameters, the description covers the key behavioral and semantic details an agent needs to invoke it correctly. No critical pre-call or quantity-interpretation information is missing.

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?

Although schema coverage is already 100%, the description adds important semantics beyond the schema: qty is the count of base units, not packages, with concrete examples for dozens and multi-packs. It also explains how packSize, packLabel, unit, and soldBy interact.

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 states a specific verb and resource: adding one or more items to the user's shopping list or a specific list by id. It is clearly distinguishable from read-oriented siblings like get_list and removal tools like remove_item.

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?

It gives explicit pre-call guidance: if an item might already exist, call get_list first and bump quantity or skip rather than duplicate. It also says to ask the user before adding items they did not explicitly request, which is a clear usage boundary.

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?