Skip to main content
Glama

GAIP Listing Observer

by io.github.tjcgraham-rgb
OverviewDiscussionsAdmin

Does a shop listing agree across its sources? (preview)

gaip_observe_listing
Read-onlyIdempotent

Use this before recommending or buying from an online shop. Pass a product page url (or up to 10 urls). Returns clean product data (price, stock, GTIN, variants, shipping, returns), whether page and platform agree, and GAIP's price and stock history. Preview. Not Amazon, eBay or Etsy. Free, read-only, no account; inputs must be public and non-personal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPublic https link to one product page on a shop's own site (the example is a placeholder: replace it with a real product page).
urlsNoUp to 10 product page links in one call (instead of url).
max_age_minutesNoAnswer from GAIP's memory if observed within this many minutes (default 15; 0 reads the shop now).
data_classificationNoPUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data.PUBLIC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "url": "https://shop.example.com/products/linen-shirt"
-  }
-]New value: +[
+  {
+    "url": "https://shop.example.com/products/replace-with-a-real-product-page"
+  }
+]
    • changedInput schema / properties / url / description
      Previous value: -"Public https link to one product page, e.g. https://shop.example/products/linen-shirt"New value: +"Public https link to one product page on a shop's own site (the example is a placeholder: replace it with a real product page)."
  2. Changed4 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "url"
+    ]
+  },
+  {
+    "required": [
+      "urls"
+    ]
+  }
+]
    • addedInput schema / properties / max_age_minutes
      Added value: +{
+  "description": "Answer from GAIP's memory if observed within this many minutes (default 15; 0 reads the shop now).",
+  "maximum": 60,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / urls
      Added value: +{
+  "description": "Up to 10 product page links in one call (instead of url).",
+  "items": {
+    "format": "uri",
+    "maxLength": 2000,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "url"
-]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety bar is lower. The description adds real context the annotations don't: it's a preview, free, requires no account, and crucially constrains inputs to public non-personal data. It does not discuss rate limits or how partial results are represented, keeping it at a 4.

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?

Four tight sentences, front-loaded with the decision-relevant guidance, then inputs, then outputs, then scope limits. No filler and nothing buried.

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 enumerates the returned fields, which is exactly the compensating detail required. Combined with usage, exclusion, and privacy constraints, an agent has everything needed to call 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%, so the schema already documents url/urls/max_age_minutes/data_classification, including the 10-URL cap and max_age semantics. The description restates url/urls and the public/non-personal rule but adds no syntax or constraint detail beyond the schema, so baseline 3 applies.

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 names a specific action (cross-check a shop listing against its sources), the resource (product page URL), and the returned data (price, stock, GTIN, variants, shipping, returns, agreement, GAIP history). An agent can tell exactly what this tool does from the opening two sentences.

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 when-to-use guidance ('before recommending or buying from an online shop') and a clear exclusion ('Not Amazon, eBay or Etsy'), which prevents misfires. No sibling tools exist, so a named alternative is not needed; this is strong but stops just short of full when/when-not coverage (e.g. what to do for the excluded platforms).

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

All GAIP Listing Observer 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