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.
`rating`	Yes	Average user rating, 0-5.
`best_offer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds that it returns the product's best offer for the given country, which is useful. However, it does not disclose behavior for not-found cases or per-language differences, leaving some gaps beyond the annotation coverage.

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 three sentences: first states the main action, second provides usage guidance, third summarizes the result. Every sentence earns its place with no redundancy or fluff.

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

Completeness3/5

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

The tool is simple and has an output schema and good annotations, so the description need not cover return values. Core usage is explained well, but the language parameter is entirely omitted and edge behaviors (e.g. no match) are not mentioned, making it not fully complete.

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 67% (id and country described). The description enhances id by specifying GTIN/EAN/UPC barcode and Ponito product id, and frames country as determining country-specific offers. However, the language parameter has no schema description and is not mentioned in the description, leaving that parameter under-specified.

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?

The description clearly states the tool 'looks up one product' by specific identifiers (GTIN/barcode or Ponito product id), making the verb and resource explicit. It also distinguishes this from sibling search_products by noting it is for when you already know exactly which product you mean.

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?

The description gives clear context for when to use the tool ('when you already know exactly which product you mean') with practical examples. It does not explicitly name alternatives or exclusion criteria, but the 'use this when' phrasing implicitly contrasts with search behavior, so it is clear.

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?