OurGroceries MCP

add_item

Add an item to a grocery list with optional quantity and note. Specify list name and item to update your OurGroceries shopping list.

Instructions

Immediately add an item to a grocery list, optionally with quantity and note.

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": {
      "list_name": "<list_name>",
      "item": "<item>"
    },
    "name": "add_item"
  }
}

Input Schema

Name	Required	Description	Default
`item`	Yes
`note`	No
`quantity`	No
`list_name`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the mutation (add) and optional fields, but doesn't describe side effects, error behavior, idempotency, or what happens if the list doesn't exist. For a mutation tool with empty annotations, this is a significant gap.

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 a single sentence that front-loads the action ('Immediately add an item'). Every word earns its place, with no unnecessary detail or repetition of schema information. It's appropriately sized for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and an output schema exists, so return values don't need to be explained. However, the description lacks behavioral context such as duplicate handling, list existence requirements, or error behavior. With empty annotations and sparse schema, this is barely adequate for a low-complexity mutation tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions quantity and note as optional, which aligns with the schema defaults, but it doesn't explain list_name or item semantics beyond their obvious names. The required parameters are not described further, providing only partial compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('add an item to a grocery list') with a specific verb and resource. It doesn't explicitly name alternatives, but the action verb distinguishes it from sibling tools like complete_item, remove_item, and move_item. Overall, it's clear but lacks explicit sibling differentiation.

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

Usage Guidelines3/5

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

The description implies this tool is used when adding an item to a grocery list, but it doesn't provide explicit guidance on when to use it versus alternatives (e.g., when to use get_items or remove_item). It also doesn't mention prerequisites like whether the list must already exist. This is implied usage without clear exclusions.

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

Deploy Server