ForthClear Liquidation Marketplace

Get product details

get_product_details

Read-only

Get detailed information about a specific product

Input Schema

TableJSON Schema

Name	Required	Description	Default
`product_id`	Yes	Product ID (format: product_123)

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`price`	Yes	Unit price in minor units of currency.
`seller`	No
`category`	Yes
`currency`	No
`condition`	No
`description`	No
`next_action`	No
`quote_required`	Yes
`original_retail`	No
`instant_checkout`	No
`payment_readiness`	No
`quantity_available`	Yes
`quote_quantity_threshold`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 17, 2026
- addedOutput schema / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / instant_checkout
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / next_action
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / payment_readiness
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / price / description
```
Previous value: -"Unit price in cents."New value: +"Unit price in minor units of currency."
```
- addedOutput schema / properties / quote_quantity_threshold
```
Added value: +{
+  "type": "integer"
+}
```

Changed1 schema field changedAug 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "type": "string"
+    },
+    "condition": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "original_retail": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "price": {
+      "description": "Unit price in cents.",
+      "type": "integer"
+    },
+    "quantity_available": {
+      "type": "integer"
+    },
+    "quote_required": {
+      "type": "boolean"
+    },
+    "seller": {
+      "properties": {
+        "company": {
+          "type": "string"
+        },
+        "verified": {
+          "description": "True once the seller has a Stripe account.",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "company",
+        "verified"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "category",
+    "quantity_available",
+    "price",
+    "quote_required"
+  ],
+  "type": "object"
+}

First observedAug 21, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds no behavioral context such as required permissions, rate limits, or the nature of the returned details. It does not contradict the annotations, but it provides no additional transparency beyond what structured fields already convey.

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, direct sentence with zero filler. It front-loads the action and resource, making it immediately clear what the tool does. There is no unnecessary elaboration.

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 well-documented parameter and an existing output schema, the description is adequate. It states the purpose clearly, the parameter is fully defined in the schema, and return values are presumably covered by the output schema. However, it could be slightly more explicit about the scope of 'detailed information' (e.g., which fields are included), though that is likely captured in the output schema.

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?

The input schema has 100% description coverage because product_id is described as 'Product ID (format: product_123)'. The tool description does not add any extra meaning or context about the parameter, so it remains at the baseline of 3 for high schema coverage.

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 a specific verb (Get) and resource (product details), and narrows scope to 'a specific product' which implies retrieval by ID. This distinguishes it from sibling tools like search_inventory (which lists products) or get_pricing_recommendation (focused on pricing). However, it does not explicitly name alternatives, so it falls short of a perfect 5.

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?

The description provides no guidance on when to use this tool versus its siblings. It does not mention search_inventory for finding products or get_pricing_recommendation for pricing, nor does it state any exclusions or conditions. An agent is left to infer usage purely from the name and description, which is minimal.

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

All ForthClear Liquidation Marketplace 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?