Skip to main content
Glama

product-intelligence

by com.ponito
OverviewDiscussionsAdmin

Search Products Tool

search_products
Read-onlyIdempotent

Search Ponito's product catalogue. Call this for any shopping query — finding products, comparing options, or checking who sells something in a given country. Returns GTIN-anchored products with their best offer (lowest price, integer minor units) and shop count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo"relevance" (popularity-weighted, default) or "cheapest" (lowest price first).relevance
limitNoMax results, 1-25.
queryYesWhat the shopper is looking for, e.g. "quiet robot vacuum" or "Bosch dishwasher 60cm".
countryYesThe shopper's country (offers and prices are country-specific).
languageNoLanguage to search and label results in.en

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
productsYesMatching products, most relevant (or cheapest) first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / products / items / properties / image
      Added value: +{
+  "description": "Product photo, served from Ponito.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / products / items / required
      Previous value: -[
-  "id",
-  "name",
-  "brand",
-  "gtins",
-  "rating",
-  "best_offer",
-  "url"
-]New value: +[
+  "id",
+  "name",
+  "brand",
+  "gtins",
+  "rating",
+  "image",
+  "best_offer",
+  "url"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "CH",
-  "DE",
-  "FR",
-  "GB"
-]New value: +[
+  "CH",
+  "DE",
+  "FR",
+  "GB",
+  "AT",
+  "ES",
+  "NL"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "de",
-  "fr",
-  "en"
-]New value: +[
+  "de",
+  "fr",
+  "en",
+  "it",
+  "es",
+  "pt",
+  "nl"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "en",
-  "de",
-  "fr"
-]New value: +[
+  "de",
+  "fr",
+  "en"
+]
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "products": {
+      "description": "Matching products, most relevant (or cheapest) first.",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "products"
+  ],
+  "type": "object"
+}
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description goes beyond them by disclosing the return shape (GTIN-anchored results, best offer, shop count) and the price format (integer minor units), which an agent otherwise could not infer from the annotations. It stops short of noting result-cap or pricing caveats.

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 tight sentences: purpose, when to call, and what comes back. Nothing is wasted and the identity of the resource is front-loaded in the first four words.

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 a full output schema, rich annotations, and 100% parameter coverage, the only missing piece was intent and result shape, both of which the description supplies. An agent has everything needed to select and invoke it correctly.

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 description coverage is 100%, with clear descriptions and enum values for sort, limit, country, and language, so the schema carries the parameter semantics. The description adds nothing about parameter usage or interactions (e.g., sort vs. limit trade-offs), so the baseline 3 applies.

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 opening sentence names a specific verb and resource ("Search Ponito's product catalogue") and the closing sentence states what results contain (GTIN-anchored products with best offer and shop count). It is clear what the tool does, but it never names or contrasts against the sibling tools get_product and get_price_history, which is what would push this to a 5.

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 explicit usage contexts: "finding products, comparing options, or checking who sells something in a given country." That is strong when-to-use guidance, but there is no when-not guidance and no pointer to the sibling lookup/history tools for narrower needs.

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

All product-intelligence toolsInspect
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