io.github.AndrewVG23/grocery-mcp

create_grocery_order_template

Create a reusable grocery list template by providing a retailer and items, for future reference without searching or placing an order.

Instructions

Save a reusable grocery list without searching or placing an order.

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": {
      "name": "<name>",
      "retailer": "<retailer>",
      "items": "<items>"
    },
    "name": "create_grocery_order_template"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`items`	Yes
`retailer`	Yes
`location_id`	No
`postal_code`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the basic function and omits details like whether existing templates are overwritten, authentication requirements, or side effects. With such minimal disclosure, the agent gets little insight into behavior beyond the high-level action.

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, front-loaded sentence with no redundant words. Every word contributes to the core purpose, making it appropriately concise for its content.

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

Completeness2/5

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

Given the tool has 5 parameters and no annotations, a one-sentence description is insufficient. It does not explain how this template creation differs from creating a handoff, nor does it offer essential context about the output or prerequisites. The output schema exists, so return values don't need explanation, but broader usage context is still missing.

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 coverage is 0% and the description provides almost no parameter-level meaning. It mentions 'grocery list' which hints at the 'items' parameter, but does not explain the expected format, the role of 'retailer', or optional fields like 'location_id' and 'postal_code'. The description fails to compensate for the lack of schema descriptions.

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 clearly states the tool saves a reusable grocery list, using a specific verb ('save') and resource ('grocery list'). It distinguishes itself from siblings by explicitly noting 'without searching or placing an order', which sets it apart from search and order-related tools.

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

Usage Guidelines4/5

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

The description provides clear context: it is for saving reusable lists and explicitly states what it does not do (searching or placing an order). This gives a when-not instruction, though it does not name alternative tools such as search_grocery_products or create_grocery_handoff.

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

Deploy Server