product-intelligence

Get Product Tool

get_product

Read-onlyIdempotent

Look up one product by GTIN (EAN/UPC barcode) or Ponito product id. Use this when you already know exactly which product you mean — e.g. from a barcode, a previous search result, or a product page. Returns the product with its best offer in the given country.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	A GTIN (8-14 digit EAN/UPC barcode) or a Ponito product id.
`country`	Yes	The shopper's country (offers and prices are country-specific).
`language`	No		en

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Ponito product id.
`url`	Yes	Ponito product page listing all offers in the country.
`name`	Yes
`brand`	Yes
`gtins`	Yes	GTIN (EAN/UPC) barcodes.
`image`	Yes	Product photo, served from Ponito.
`rating`	Yes	Average user rating, 0-5.
`best_offer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedOutput schema / properties / image

Added value: +{
+  "description": "Product photo, served from Ponito.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "name",
-  "brand",
-  "gtins",
-  "rating",
-  "best_offer",
-  "url"
-]New value: +[
+  "id",
+  "name",
+  "brand",
+  "gtins",
+  "rating",
+  "image",
+  "best_offer",
+  "url"
+]

Changed1 schema field changedAug 12, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "CH",
-  "DE",
-  "FR",
-  "GB"
-]New value: +[
+  "CH",
+  "DE",
+  "FR",
+  "GB",
+  "AT",
+  "ES",
+  "NL"
+]

Changed1 schema field changedAug 11, 2026

changedInput schema / properties / language / enum

Previous value: -[
-  "de",
-  "fr",
-  "en"
-]New value: +[
+  "de",
+  "fr",
+  "en",
+  "it",
+  "es",
+  "pt",
+  "nl"
+]

Changed1 schema field changedAug 6, 2026

changedInput schema / properties / language / enum

Previous value: -[
-  "en",
-  "de",
-  "fr"
-]New value: +[
+  "de",
+  "fr",
+  "en"
+]

Changed1 schema field changedAug 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "best_offer": {
+      "properties": {
+        "currency": {
+          "type": "string"
+        },
+        "price": {
+          "description": "Lowest current price in minor units (cents/rappen).",
+          "type": "integer"
+        },
+        "shops_count": {
+          "description": "Number of shops currently offering the product.",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "price",
+        "currency",
+        "shops_count"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "brand": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "gtins": {
+      "description": "GTIN (EAN/UPC) barcodes.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "id": {
+      "description": "Ponito product id.",
+      "type": "string"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rating": {
+      "description": "Average user rating, 0-5.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "Ponito product page listing all offers in the country.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "brand",
+    "gtins",
+    "rating",
+    "best_offer",
+    "url"
+  ],
+  "type": "object"
+}

First observedAug 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond the annotations: the response is the product with its best offer, and that offer is country-scoped. Still silent on failure modes (invalid GTIN, product not carried in a country), which keeps it short of 5.

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 sentences, front-loaded with identity and lookup form, then usage condition, then return shape. No filler and no repetition of schema content beyond what is needed.

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?

An output schema exists, so return structure need not be spelled out, and the description correctly limits itself to the offer/country nuance. The only uncovered item is the language parameter's effect on returned text, which the description never mentions.

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 67%, and the description adds meaning the schema lacks by explaining why country is required ('offers and prices are country-specific'), which is the key semantic for choosing that enum value. The id formats it restates are already in the schema, so it does not fully carry the undocumented language parameter.

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?

Opens with a specific verb+resource ('Look up one product') and names the two accepted identifier forms (GTIN/EAN/UPC or Ponito product id). Combined with the singular 'one product' framing, an agent can immediately distinguish this from the sibling search_products.

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?

Provides clear positive guidance: 'Use this when you already know exactly which product you mean — e.g. from a barcode, a previous search result, or a product page.' That implicitly excludes the search path but never names search_products or states the exclusion explicitly, so it falls short of a 5.

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

All product-intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?