mcp-gateway

get_product_details

Read-onlyIdempotent

Get detailed information about a specific product in Demo Store, including all variants, sizes, colors, and availability.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`product_id`	Yes	Product ID — use the `id` field returned by search_products or nlweb_ask (e.g. 'prod-snk-001'). Do not invent IDs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`url`	No
`tags`	No
`error`	No
`price`	No
`title`	No
`jsonLd`	No
`vendor`	No
`message`	No
`currency`	No
`variants`	No
`image_url`	No
`attributes`	No
`categories`	No
`product_id`	No
`review_count`	No
`stock_status`	No
`average_rating`	No
`compare_at_price`	No
`rating_provenance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 17, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

changedOutput schema / properties / rating_provenance / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "note": {
-        "type": "string"
-      },
-      "origin": {
-        "const": "merchant",
-        "type": "string"
-      },
-      "strength": {
-        "const": "claimed",
-        "type": "string"
-      },
-      "verified": {
-        "const": false,
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "origin",
-      "strength",
-      "verified",
-      "note"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "note": {
+        "type": "string"
+      },
+      "origin": {
+        "const": "merchant",
+        "type": "string"
+      },
+      "strength": {
+        "const": "claimed",
+        "type": "string"
+      },
+      "verified": {
+        "const": false,
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "origin",
+      "strength",
+      "verified",
+      "note"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / variants / items / additionalProperties
```
Previous value: -falseNew value: +true
```

Changed1 schema field changedSep 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "attributes": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "average_rating": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "categories": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "compare_at_price": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "currency": {
+      "type": "string"
+    },
+    "error": {
+      "const": "not_found",
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "image_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "jsonLd": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "price": {
+      "type": "number"
+    },
+    "product_id": {
+      "type": "string"
+    },
+    "rating_provenance": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "note": {
+              "type": "string"
+            },
+            "origin": {
+              "const": "merchant",
+              "type": "string"
+            },
+            "strength": {
+              "const": "claimed",
+              "type": "string"
+            },
+            "verified": {
+              "const": false,
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "origin",
+            "strength",
+            "verified",
+            "note"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "review_count": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "stock_status": {
+      "enum": [
+        "in_stock",
+        "low_stock",
+        "out_of_stock"
+      ],
+      "type": "string"
+    },
+    "tags": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "variants": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "options": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "price": {
+            "type": "number"
+          },
+          "sku": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "stock_status": {
+            "enum": [
+              "in_stock",
+              "low_stock",
+              "out_of_stock"
+            ],
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "price",
+          "sku",
+          "stock_status",
+          "options"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "vendor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedAug 24, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties

Added value: +{
+  "product_id": {
+    "description": "Product ID — use the `id` field returned by search_products or nlweb_ask (e.g. 'prod-snk-001'). Do not invent IDs.",
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[
+  "product_id"
+]
```

Changed4 schema fields changedJul 10, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```

removedInput schema / properties

Removed value: -{
-  "product_id": {
-    "description": "Product ID — use the `id` field returned by search_products or nlweb_ask (e.g. 'prod-snk-001'). Do not invent IDs.",
-    "type": "string"
-  }
-}

removedInput schema / required
```
Removed value: -[
-  "product_id"
-]
```

First observedApr 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds value by specifying the scope of details (variants, sizes, colors, availability), which goes beyond annotations. No contradiction is present, and the description aligns with the read-only nature.

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 a single, well-structured sentence. It front-loads the core action and resource, then expands with the detail categories. There is no filler or redundancy; every element earns its place.

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 simple read-only tool with one parameter and an output schema, the description is largely complete. It states the tool's scope and the kind of data returned. The only gap is the lack of explicit routing to sibling tools (e.g., how to obtain product_id), but given the schema already covers that, the overall context is sufficient.

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 the product_id parameter well (including the instruction to use the id field from search_products). The description does not add any additional parameter-level information; it relies entirely on the schema. 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 description clearly states the action ('Get detailed information') and the specific resource ('a specific product in Demo Store'), and even enumerates the details include variants, sizes, colors, and availability. It distinguishes from the search sibling tools (which return lists) by focusing on a single product, though it does not name an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives. It does not mention that search_products should be used first to find product IDs, nor does it note any exclusions (e.g., 'not for listing multiple products'). Usage context is entirely implied by the tool name and description.

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

All mcp-gateway 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?