Skip to main content
Glama

grocery_cheapest

Read-only

Ranks grocery chains by current price to compare product costs across stores, counting only prices checked within 14 days.

Instructions

Which chain is cheapest? Ranks the chains by their current price from Kassalapp; a price unchecked for 14 days never counts. 'product' is the words the person said, such as 'kaffe', or the name or barcode ('ean') of a choice the last answer offered.

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_cheapest"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds genuinely new behavioral information: a staleness rule that a price unchecked for 14 days never counts, which directly affects result trustworthiness. It does not cover fallback behavior when no fresh price exists, but the freshness disclosure is real value beyond the annotation.

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?

Three short sentences with zero filler: the purpose question leads, the ranking and freshness rule follow, and the parameter guidance closes. Each sentence carries distinct information and nothing is repeated from the schema or annotations.

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 single-parameter read-only tool with an output schema, the definition covers purpose, data freshness, and argument sourcing. Minor gaps remain, such as geographic scope of the chains compared or behavior when no chain has a fresh price, but nothing essential for correct invocation is missing.

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?

Schema description coverage is 0%, so the description must carry the parameter, and it does: 'product' accepts natural-language words ('kaffe'), a product name, or a barcode/EAN referring to a choice from the previous answer. That is meaning well beyond a bare string field and clarifies the mixing of free text and identifiers.

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?

Starts with a specific question ('Which chain is cheapest?') and follows with a concrete verb+resource: 'Ranks the chains by their current price from Kassalapp.' That is clearly a cross-chain comparison rather than a single-price lookup, which distinguishes it in intent from grocery_price, though the sibling is never named explicitly.

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?

Usage is implied through the framing question and the note that 'product' can be 'the words the person said' or a choice offered by the last answer, which tells the agent how to source the argument in a conversation. However, there is no explicit statement of when to choose this over grocery_price, nor any exclusion or failure condition.

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