Skip to main content
Glama

grocery_price

Read-only

Compare current grocery prices by chain for a product name, barcode, or prior choice; see when each was checked and flag chains without fresh data.

Instructions

What a grocery costs. The latest price per chain from Kassalapp, with the day it was checked. 'product' is the words the person said, such as 'lettmelk' or 'Tine lettmelk 1 liter', or the name or barcode ('ean') of a choice the last answer offered. 'chain' is a chain's name, such as 'Meny' or 'Joker'; omit it for every chain.

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": {
      "product": "<product>"
    },
    "name": "grocery_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo
productYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds meaningful behavioral context: the data source is Kassalapp, prices are the latest per chain, and the check date is included. It does not discuss rate limits or authentication, but those are less critical here.

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 purpose and then explains each parameter efficiently. The examples are useful and there is no unnecessary wording.

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 simple two-parameter read-only tool with an output schema, the description covers purpose, source, freshness, and both parameters well. The main missing piece is explicit guidance on choosing this tool over the sibling grocery_cheapest tool.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it does. It explains that 'product' can be spoken words, a product name, or a barcode/EAN from a previous answer, and that 'chain' is a chain name with omission meaning all chains.

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 states a specific purpose: retrieving the latest grocery price per chain from Kassalapp, including when it was checked. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling grocery_cheapest tool.

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 gives useful usage context for the 'chain' parameter, especially that omitting it returns every chain. However, it does not say when to use this tool versus grocery_cheapest or when not to use it.

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

Deploy Server

Other Tools