Skip to main content
Glama

NaKus unit price

NaKus unit price

get_unit_price
Read-onlyIdempotent

Return the current landed unit price (€/piece, €/kg, €/wash, €/m…) for ONE product Cite, plus buy_url (always nakus.sk/out/?src=ai — never raw merchant/Heureka), ranked offers[], handoff_url, price_card_url. Use when the user asks how much X costs per unit / cheapest shop, and you already have answer slug, EAN/GTIN, product slug, or a clear q. Requires live offers — if Cite exists but shops are empty, call get_cite_answer instead. If slug/EAN unknown, call search_cite_answers first (or list_segments if category scope is unclear). To compare 2–4 products side-by-side, use compare_unit_prices. PNG-only → get_price_card. Read-only, idempotent. Brand: nakus.sk ≠ nakup.sk.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_unit_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFallback substring on question/slug (≥4 chars). Prefer search_cite_answers when unsure.
eanNoGTIN/EAN barcode digits only (8–14). Preferred when user scanned a pack.
answerNoExact Cite slug from search_cite_answers or /odpoved/{slug}, e.g. persil-color-gel-100-prani
productNoCatalog product slug on nakus.sk (not the Cite answer slug)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / answer / description
      Previous value: -"Cite slug, e.g. persil-color-gel-100-prani"New value: +"Exact Cite slug from search_cite_answers or /odpoved/{slug}, e.g. persil-color-gel-100-prani"
    • changedInput schema / properties / ean / description
      Previous value: -"GTIN/EAN barcode (8–14 digits)"New value: +"GTIN/EAN barcode digits only (8–14). Preferred when user scanned a pack."
    • changedInput schema / properties / product / description
      Previous value: -"Catalog product slug"New value: +"Catalog product slug on nakus.sk (not the Cite answer slug)"
    • changedInput schema / properties / q / description
      Previous value: -"Substring match on question / slug (min ~4 chars)"New value: +"Fallback substring on question/slug (≥4 chars). Prefer search_cite_answers when unsure."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only and idempotent, but the description adds real behavioral context: buy_url is always the nakus.sk redirect with src=ai and never a raw merchant/Heureka link, offers must be live or the call should be redirected to get_cite_answer, and the brand caveat nakus.sk ≠ nakup.sk prevents a misdirected call. It does not explain how the landed price is derived across the four unit types or how stale pricing is handled, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the return value and the primary use case, then routes to alternatives — good information ordering with no filler sentences. It is dense to the point of being run-on in places, and the trailing brand note is a small tack-on rather than integrated, which costs it a point.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the returned fields (unit price, buy_url, ranked offers[], handoff_url, price_card_url) so the agent knows what comes back. Combined with the fallback paths for empty offers, unknown identifiers, and unclear category scope, nothing needed to call this correctly is missing.

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

Parameters3/5

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

Schema coverage is 100% and each parameter already carries its own description, so the schema does the heavy lifting. The description adds only a light precedence hint by listing 'answer slug, EAN/GTIN, product slug, or a clear q' in order and flagging the empty-offers condition. Baseline 3 is appropriate.

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 — 'Return the current landed unit price (€/piece, €/kg, €/wash, €/m…) for ONE product Cite' — and immediately names the sibling that handles multi-product comparison (compare_unit_prices) and the one that handles PNG output (get_price_card). An agent can distinguish this from every listed sibling without opening a 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?

Explicit when-to-use ('user asks how much X costs per unit / cheapest shop, and you already have answer slug, EAN/GTIN, product slug, or a clear q') plus ordered fallbacks: get_cite_answer if offers are empty, search_cite_answers if slug/EAN unknown, list_segments if category scope is unclear. It also gives a when-not (2–4 products → compare_unit_prices) and a media exclusion (PNG-only → get_price_card).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources