listonic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| Listonic__Email | Yes | Your Listonic account email. | |
| Listonic__Password | Yes | Your Listonic account password. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_listsA | List every shopping list the user can access (own and shared). Returns one line per list as "[listId] name (private|shared) - N unchecked". Call this first - every other tool needs a listId from here. Match the user's wording to a list name; if more than one list could fit, ask which one. This server has no categories or item notes and can't create lists or move items between lists - say so instead of looking for another tool. |
| get_itemsA | Get every item on one list. Unchecked items (still to buy) come first, then checked ones (bought / ticked off), each as "[ ] [itemId] name (amount unit)" or "[x] …". When the user asks what to buy, report only unchecked items; mention checked ones only if asked. Call this before edit_items or delete_items to get itemIds, and before add_items to avoid duplicates. Several rows can share a name. When the user names such an item, tick or untick every row the change applies to (only unchecked rows when ticking off). Before deleting it or changing its amount, consider only unchecked rows unless the user means a checked one: if one row matches, act on it; if several match, ask which one. |
| add_itemsA | Add one or more items to a list in a single call; new items start unchecked. Put only the product in name (in the user's language, e.g. "mleko"), the number in amount and the unit in unit - never the quantity inside the name. Before adding, call get_items and check whether the item already exists. If it's checked, untick it and set the amount the user gave. If it's unchecked, ask whether to add to its amount or replace it. Don't create a duplicate row. Returns the added items in get_items format. |
| edit_itemsA | Change items already on a list: tick them off when bought (isChecked: true), untick (false), rename, or change amount/unit. "I bought X" = tick it off, do not delete. Send only the fields to change; omitted or null fields stay as they are; send amount 0 and unit "" to clear the quantity. Get itemIds from get_items. Items can't be moved between lists - add to target list and delete from source. Batch: send all items to change in one call. Returns the updated items in get_items format. |
| delete_itemsA | Permanently delete items from a list; this can't be undone. To mark something as bought, tick it off with edit_items instead. Use this when the user wants an item gone (added by mistake, no longer needed) or asks to clear bought items - then delete only the checked ones. Before deleting more than a few items or emptying a whole list, confirm with the user. Get itemIds from get_items. Always pass confirmName alongside each itemId. Returns the deleted items in get_items format. |
| rename_listA | Rename an existing shopping list. On a shared list the new name is visible to everyone who shares it. This server can't create lists - tell the user to do that in the Listonic app. |
| delete_listA | Move a whole shopping list to the Listonic trash; it can be restored from the trash in the app. On a shared list this removes it for everyone who shares it - get_lists shows whether a list is shared. Always confirm with the user, naming the list, before calling. To delete items but keep the list, use delete_items instead. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: lists versus items, and get/add/edit/delete/rename operations. The descriptions explicitly clarify the main potential confusion points, such as edit_items ticking off an item versus delete_items removing it, and delete_items versus delete_list. An agent should reliably select the correct tool.
All tool names follow a consistent verb_noun pattern using snake_case: get_lists, get_items, add_items, edit_items, delete_items, rename_list, delete_list. Plural versus singular nouns are used predictably according to whether the operation acts on one list or multiple items.
Seven tools are well scoped for a shopping-list management server. Each tool covers a distinct operation without redundancy, and the set is small enough to remain easy to navigate while covering the core list and item workflows.
Item operations are essentially complete: get, add, edit, tick/untick, and delete are all covered. The main gaps are the inability to create lists and to move items between lists, but the descriptions explicitly acknowledge these limitations and point users to the Listonic app, so agents can work around them.