Skip to main content
Glama

ForthClear Liquidation Marketplace

Get product details

get_product_details
Read-only

Read one listing: description, price, quantity, condition, photo, and whether instant checkout is available. No sign-in required. Use this before requesting a quote or buying. Pass the exact id from search, for example product_2731.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_product_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias for product_id.
slugNoAlias for product_id. Public listing slug, such as surplus-lot-2731.
productIdNoAlias for product_id.
product_idNoExact id from search, for example product_2731. productId, id, and slug are aliases.

Output Schema

NameRequiredDescriptionDefault
idYes
moqNo
urlYesAbsolute URL of the public listing page.
nameYes
priceYesUnit price in minor units of currency.
sellerNo
categoryYes
currencyNo
lot_typeNo
supplierNoPresent when this listing's seller has claimed a published supplier profile.
conditionNo
image_urlNoAbsolute https URL of the primary photo, or null when the listing has none.
next_stepNo
ship_fromNo
terms_urlNo
sold_as_isNo
descriptionNoPlain-text listing copy. HTML and citation markers are removed.
next_actionNo
claims_summaryNo
quote_requiredYesTrue when this listing has no quantity that can be paid directly. It is not 'the lot has more than 100 units'. Orders at or above quote_quantity_threshold still need a quote even when this is false. The charge path still confirms the seller can take a card.
shipping_priceNoPer-unit shipping as a number, or the string quote shipping.
original_retailNo
quote_thresholdNo
shipping_methodNo
bulk_price_tiersNo
instant_checkoutNo
claims_policy_urlNo
payment_readinessNo
ship_from_countryNo
min_order_quantityNo
quantity_availableYes
condition_definitionNo
shipping_price_centsNoPer-unit freight in cents, or null when not priced.
quote_quantity_thresholdNo
instant_checkout_eligibleNo
requires_verified_resellerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Alias for product_id"New value: +"Alias for product_id."
    • changedInput schema / properties / productId / description
      Previous value: -"Alias for product_id"New value: +"Alias for product_id."
    • changedInput schema / properties / product_id / description
      Previous value: -"Exact id from search, for example product_2731"New value: +"Exact id from search, for example product_2731. productId, id, and slug are aliases."
    • addedInput schema / properties / slug
      Added value: +{
      +  "description": "Alias for product_id. Public listing slug, such as surplus-lot-2731.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / quote_required / description
      Added value: +"True when this listing has no quantity that can be paid directly. It is not 'the lot has more than 100 units'. Orders at or above quote_quantity_threshold still need a quote even when this is false. The charge path still confirms the seller can take a card."
  3. Changed1 schema field changed
    • changedOutput schema / properties / seller / properties / verified / description
      Previous value: -"True when a Stripe account id is on file. It does not mean payouts are enabled. Payment readiness is checked at checkout."New value: +"True only when the cached Stripe account can take charges and payouts. A mapped account that cannot charge is false. This is not the viewer's sign-in state."
  4. Changed23 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "Alias for product_id",
      +  "type": "string"
      +}
    • addedInput schema / properties / productId
      Added value: +{
      +  "description": "Alias for product_id",
      +  "type": "string"
      +}
    • changedInput schema / properties / product_id / description
      Previous value: -"Product ID (format: product_123)"New value: +"Exact id from search, for example product_2731"
    • removedInput schema / required
      Removed value: -[
      -  "product_id"
      -]
    • addedOutput schema / properties / bulk_price_tiers
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "min_quantity": {
      +        "type": "integer"
      +      },
      +      "price_cents": {
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "min_quantity",
      +      "price_cents"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / claims_policy_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / claims_summary
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / condition_definition
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / instant_checkout_eligible
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / lot_type
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / min_order_quantity
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / moq
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / next_step
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / quote_threshold
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / requires_verified_reseller
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / ship_from
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / ship_from_country
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / shipping_method
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / shipping_price
      Added value: +{
      +  "description": "Per-unit shipping as a number, or the string quote shipping.",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedOutput schema / properties / shipping_price_cents
      Added value: +{
      +  "description": "Per-unit freight in cents, or null when not priced.",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / sold_as_is
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / supplier
      Added value: +{
      +  "description": "Present when this listing's seller has claimed a published supplier profile.",
      +  "properties": {
      +    "country": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "slug": {
      +      "type": "string"
      +    },
      +    "type": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "slug",
      +    "country",
      +    "type",
      +    "url"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / terms_url
      Added value: +{
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / properties / seller / properties / verified / description
      Previous value: -"True once the seller has a Stripe account."New value: +"True when a Stripe account id is on file. It does not mean payouts are enabled. Payment readiness is checked at checkout."
  6. Changed4 schema fields changed
    • addedOutput schema / properties / description / description
      Added value: +"Plain-text listing copy. HTML and citation markers are removed."
    • addedOutput schema / properties / image_url
      Added value: +{
      +  "description": "Absolute https URL of the primary photo, or null when the listing has none.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / url
      Added value: +{
      +  "description": "Absolute URL of the public listing page.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "category",
      -  "quantity_available",
      -  "price",
      -  "quote_required"
      -]New value: +[
      +  "id",
      +  "name",
      +  "category",
      +  "quantity_available",
      +  "price",
      +  "quote_required",
      +  "url"
      +]
  7. Changed6 schema fields changed
    • 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"
      +}
  8. Changed1 schema field changed
    • 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"
      +}
  9. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful non-annotation context: no sign-in is required and the response will reveal whether instant checkout is available, which shapes downstream decisions.

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 short sentences, front-loaded with the returned fields, then access constraint, then usage, then the invocation hint. No sentence is redundant and all of them carry information.

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?

Output schema and annotations are supplied, so return values and safety need not be re-explained, and the description covers the essential lookup flow. It leaves one practical gap: all four parameters are optional aliases, and the description never says only one identifier is needed or how conflicts between slug and product_id are resolved.

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?

With 100% schema coverage, the documented baseline applies, and the description only reinforces the id format with a product_2731 example already present in the schema. It does not address the ambiguity of four optional alias parameters (id, slug, productId, product_id), which is the one place added meaning would have helped an agent decide which to pass.

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 opens with a specific verb and resource ('Read one listing') and enumerates exactly what is returned: description, price, quantity, condition, photo, and instant-checkout availability. It implicitly contrasts with the search flow by telling the agent to pass 'the exact id from search', so the single-listing scope is clear, though it does not name search_inventory explicitly.

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 a clear trigger ('Use this before requesting a quote or buying'), which routes the agent ahead of request_quote and quick_buy. It does not state when not to use it or name the search tool as the alternative for browsing, so exclusions are absent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources