Skip to main content
Glama

Nutrition, ingredients and product details

get_product_details
Read-onlyIdempotent

Nutrition per 100g or 100ml (energy, fat, carbohydrate, sugars, protein, salt), the ingredients list as printed (allergens included), how many ingredients it lists, country of origin, a quality mark the pack shows (Bord Bia Quality Assured), alcohol strength, pack size, description and today's price, for particular products.

Products are looked up by product id (store-prefixed, as returned in product results), by the retailer's own item numbers (skus with store, as printed on its receipts), or by name (query). ingredients_incomplete marks an ingredient list on record that is cut short, which cannot show that an ingredient is absent. A product looked up by id or item number answers even after it has left the shop's range: in_range_today false marks one, and its price is then the last one recorded (price_date), not today's. Ids with no product on record are listed in not_found. Results carry a note that nutrition and ingredients are for information only. Each product returned costs one credit.

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

Input Schema

NameRequiredDescriptionDefault
skusNoThe shop's own item numbers, as printed on its receipts, e.g. ['100873410'], up to 50. Needs store. An Aldi article number can return several variants.
limitNoMost products to return for a query (default 5, at most 50).
queryNoProduct name words, e.g. 'kellogg's corn flakes'.
storeNoaldi, tesco, supervalu, dunnes or lidl: needed with skus; narrows a query; left out, all five.
product_idsNoProduct ids exactly as another tool gave them, e.g. ['tesco:300793546', 'dunnes:100873410', '000000000000387044'], up to 50. The sure way to name a product.

Output Schema

NameRequiredDescriptionDefault
hintNoWhat to try, when a name found nothing
noteYes
creditsNoWhat this answer cost the person's BasketWatch account and what is left. Missing on a free answer
productsNo
not_foundNoRequested product_ids with no product on record

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / $defs / ProductDetail / properties / quality_marks / description
      Previous value: -"Quality marks on record for the product, e.g. 'Bord Bia Quality Assured': read off the shop's photo of the pack, or named in the label's origin statement; missing where none is on record, which does not say the pack has none"New value: +"Quality marks on record for the product, e.g. 'Bord Bia Quality Assured' or 'Organic': read off the shop's photo of the pack, or said in the shop's own words about the product; missing where none is on record, which does not say the pack has none"
  2. Changed1 schema field changed
    • changedOutput schema / $defs / ProductDetail / properties / quality_marks / description
      Previous value: -"Quality marks the pack itself shows, read off the shop's photo of the pack, e.g. 'Bord Bia Quality Assured'; missing where none was found on the photo, which does not say the pack has none"New value: +"Quality marks on record for the product, e.g. 'Bord Bia Quality Assured': read off the shop's photo of the pack, or named in the label's origin statement; missing where none is on record, which does not say the pack has none"
  3. Changed1 schema field changed
    • addedOutput schema / $defs / ProductDetail / properties / quality_marks
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Quality marks the pack itself shows, read off the shop's photo of the pack, e.g. 'Bord Bia Quality Assured'; missing where none was found on the photo, which does not say the pack has none",
      +  "title": "Quality Marks"
      +}
  4. Changed28 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Most products to return for a query (default 5, at most 50)."
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • addedInput schema / properties / product_ids / description
      Added value: +"Product ids exactly as another tool gave them, e.g. ['tesco:300793546', 'dunnes:100873410', '000000000000387044'], up to 50. The sure way to name a product."
    • removedInput schema / properties / product_ids / title
      Removed value: -"Product Ids"
    • addedInput schema / properties / query / description
      Added value: +"Product name words, e.g. 'kellogg's corn flakes'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • addedInput schema / properties / skus / description
      Added value: +"The shop's own item numbers, as printed on its receipts, e.g. ['100873410'], up to 50. Needs store. An Aldi article number can return several variants."
    • removedInput schema / properties / skus / title
      Removed value: -"Skus"
    • changedInput schema / properties / store / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "aldi",
      +      "tesco",
      +      "supervalu",
      +      "dunnes",
      +      "lidl"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / store / description
      Added value: +"aldi, tesco, supervalu, dunnes or lidl: needed with skus; narrows a query; left out, all five."
    • removedInput schema / properties / store / title
      Removed value: -"Store"
    • removedInput schema / title
      Removed value: -"get_product_detailsArguments"
    • addedOutput schema / $defs / Credits
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "left": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Credits left on the account after it",
      +      "title": "Left"
      +    },
      +    "note": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Said when the balance is low, or when it cut this answer short",
      +      "title": "Note"
      +    },
      +    "used": {
      +      "description": "Credits this answer cost: one for each record it returned",
      +      "title": "Used",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "used"
      +  ],
      +  "title": "Credits",
      +  "type": "object"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / clubcard_price
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Member price where one applies: Tesco Clubcard, SuperValu Real Rewards or Lidl Plus",
      +  "title": "Clubcard Price"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / in_range_today
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "For a product looked up by id or item number: false when the shop's latest catalogue day does not list it, so price is its last recorded price and not a price to buy at today",
      +  "title": "In Range Today"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / offer_ends
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Last day the offer applies, YYYY-MM-DD, Irish time, where the retailer states it",
      +  "title": "Offer Ends"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / offer_text
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The offer as the shop words it",
      +  "title": "Offer Text"
      +}
    • changedOutput schema / $defs / ProductDetail / properties / price / description
      Previous value: -"Today's shelf price in euro"New value: +"Shelf price in euro on price_date: today's, unless in_range_today is false"
    • addedOutput schema / $defs / ProductDetail / properties / price_date
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The day price was recorded, YYYY-MM-DD",
      +  "title": "Price Date"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / price_per_kg
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "unit_price worked out per kilo, where the shop prices the product by weight: the figure to compare packs of different sizes on (per kilo drained, where unit_basis says drained weight)",
      +  "title": "Price Per Kg"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / price_per_litre
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "unit_price worked out per litre, where the shop prices the product by volume",
      +  "title": "Price Per Litre"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / unit_basis
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The measure unit_price is in, as the shop states it: '1 KG', '100g', '75cl', 'each'",
      +  "title": "Unit Basis"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / unit_price
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The shop's own unit price, in the measure unit_basis names: per kg at one shop, per 100g or per 75cl at another, so as it stands it does not compare across rows",
      +  "title": "Unit Price"
      +}
    • addedOutput schema / properties / credits
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/Credits"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "What this answer cost the person's BasketWatch account and what is left. Missing on a free answer"
      +}
    • addedOutput schema / properties / hint
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "What to try, when a name found nothing",
      +  "title": "Hint"
      +}
    • addedOutput schema / properties / not_found
      Added value: +{
      +  "description": "Requested product_ids with no product on record",
      +  "items": {
      +    "type": "string"
      +  },
      +  "title": "Not Found",
      +  "type": "array"
      +}
  5. Changed1 schema field changed
    • addedOutput schema / $defs / ProductDetail / properties / ingredients_source
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Where the ingredient list came from: the retailer, the same product (same barcode) at another retailer, or Open Food Facts",
      +  "title": "Ingredients Source"
      +}
  6. Changed1 schema field changed
    • addedOutput schema / $defs / ProductDetail / properties / shelf_path
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Where the retailer shelves it, every level, e.g. 'Fresh Food > Yoghurts > Kefir > Kefir Drinks'",
      +  "title": "Shelf Path"
      +}
  7. Changed1 schema field changed
    • addedOutput schema / $defs / ProductDetail / properties / alcohol_abv_source
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Where the strength came from: the retailer's own listing, worked out from its alcohol units per bottle or can, or the same barcode at another store",
      +  "title": "Alcohol Abv Source"
      +}
  8. Changed1 schema field changed
    • addedOutput schema / $defs / ProductDetail / properties / allergy_advice
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The retailer's allergy advice, kept apart from the ingredients: what the product contains and may contain, e.g. 'Contains: Milk. May contain: Nuts.'; missing where the retailer publishes none",
      +  "title": "Allergy Advice"
      +}
  9. Changed1 schema field changed
    • changedOutput schema / $defs / ProductDetail / properties / origin / description
      Previous value: -"Country of origin as stated, e.g. 'Ireland', or 'China, Spain, Argentina' for a blend; missing where none is stated"New value: +"Every country the label states, where it was made and where its main ingredient is from, e.g. 'Ireland', 'Ireland, EU, non-EU' (produced in Ireland using EU and non-EU chicken) or 'China, Spain, Argentina' for a blend; missing where none is stated"
  10. Changed3 schema fields changed
    • addedOutput schema / $defs / ProductDetail / properties / origin
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Country of origin as stated, e.g. 'Ireland', or 'China, Spain, Argentina' for a blend; missing where none is stated",
      +  "title": "Origin"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / origin_source
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Where the origin came from",
      +  "title": "Origin Source"
      +}
    • addedOutput schema / $defs / ProductDetail / properties / origin_text
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The origin statement in the source's own words",
      +  "title": "Origin Text"
      +}
  11. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations it discloses genuinely useful behaviour: in_range_today false means the product left the range and price_date holds the last recorded price, not today's; ingredients_incomplete flags a truncated ingredient list; missing ids appear in not_found; there is a per-product credit cost. That is strong context for a read-only lookup, though the description does not describe result ordering or pagination.

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

Conciseness3/5

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

The first sentence is a long comma-separated enumeration of return fields (energy, fat, carbohydrate, sugars, protein, salt...) that largely duplicates the available output schema. The subsequent sentences are dense but carry real information; the structure is front-loaded but the field catalogue is padding relative to what the output schema already provides.

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 five-parameter, optional-only lookup with an output schema, the description covers the lookup modes, the store/SKU dependency, stale-price semantics, not-found reporting and credit cost. Nothing critical is missing, though an explicit pointer to which sibling finds the ids in the first place would close the loop.

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 coverage is already 100%, so the baseline is 3, and the description still adds value by explaining the coupling of skus with store, that product ids are store-prefixed, and that name lookup takes a limit. It adds meaning beyond the schema rather than restating it.

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 names a specific resource (product details: nutrition, ingredients, origin, quality mark, pack size, price) and the three identification keys it accepts (product id, retailer SKU, name query). It clearly separates this from a discovery/search tool by stressing that ids are 'as returned in product results' and SKUs come from receipts, though it never names a sibling tool outright.

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?

It gives concrete usage context: pass ids from product results, pass SKUs together with store, or pass a name query with an optional limit and store. It also states the fallback behaviour (out-of-range products still answer) and that each returned product costs one credit. It stops short of explicitly saying when to prefer a search/find tool instead.

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