Skip to main content
Glama
picnic-mcp
by MRVDH

Find cheaper alternatives

get_cheaper_alternatives
Read-only

Find cheaper alternatives to a Picnic product by comparing similar items by unit price, lowest-priced first. Use it when a user asks for a cheaper option or wants to save on a product.

Instructions

Find cheaper versions of a Picnic product: similar products that cost less per kg, litre or piece, cheapest first. Use it when the user asks for a cheaper option or wants to save on a product. Get the product id from search_products or get_cart. It only reads; to swap a product in the cart, ask the user first.

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": {
      "productId": "<productId>"
    },
    "name": "get_cheaper_alternatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesThe product id from search_products or get_cart, e.g. s1004201.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it with "It only reads" plus the concrete safeguard about confirming with the user before swapping in the cart. It adds ordering behavior ("cheapest first") and the comparison basis (per kg, litre or piece), which the annotations do not convey. It stops short of noting result limits or what happens when no cheaper alternative exists.

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?

Four short sentences, each doing distinct work: what it returns, when to call it, where the id comes from, and the safety caveat. The most decision-relevant content (purpose and result ordering) is front-loaded with no filler.

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

Completeness4/5

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

For a read-only lookup with one required parameter and no output schema, the description covers purpose, trigger, input provenance, result ordering, and the boundary against mutation. The result shape is sketched just enough ("similar products that cost less per kg, litre or piece"). It leaves minor gaps around empty-result behavior and result count.

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

Parameters4/5

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

With a single fully documented parameter (100% schema coverage, including the ^s\d+$ pattern and an example), the schema already carries the syntax burden. The description still adds operational meaning by naming the two tools that produce a valid id, which is the one genuinely useful piece of parameter guidance here. It does not elaborate on invalid-id behavior.

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?

States a specific verb and resource ("Find cheaper versions of a Picnic product") and immediately narrows the result set to similar products with a lower unit price, sorted cheapest first. This clearly distinguishes it from siblings like get_product (single item lookup) and search_products (discovery), so an agent can select it without opening the 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?

Explicitly names the triggering user intents ("asks for a cheaper option or wants to save on a product") and tells the agent where the required productId comes from (search_products or get_cart). It also states the post-condition workflow rule: ask the user before swapping anything in the cart, which prevents an agent from chaining into a mutation unprompted.

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