ForthClear Liquidation Marketplace

Preview checkout

preview_checkout

Read-onlyIdempotent

Read the seller of record, unit price, shipping, tax, and total for an instant-checkout listing. Does not charge a card. Requires buyer read access. Pass the returned checkout_id to confirm_purchase. Requires sign-in with buyer access. OAuth discovery: /.well-known/oauth-authorization-server (scope buyer:read).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "<product_id>",
      "quantity": "<quantity>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "preview_checkout"
  }
}

Input Schema

Name	Required	Description
`id`	No	Alias for product_id.
`slug`	No	Alias for product_id. Public listing slug.
`quantity`	Yes	Units to buy. Must be below the quote threshold.
`productId`	No	Alias for product_id.
`product_id`	Yes	Exact id from search, for example product_2731. productId, id, and slug are aliases.
`idempotency_key`	Yes	Required. 8–200 characters (letters, digits, . _ : -). The same key returns the original result for 24 hours and is sent to Stripe as Idempotency-Key.
`shipping_address_id`	No	Optional. Shipping is the listing's shipping price; tax is not collected on this path.

Output Schema

Name	Required	Description
`tax`	No
`status`	Yes
`is_test`	No
`currency`	No
`quantity`	No
`tax_cents`	No
`terms_url`	No
`expires_at`	No
`preview_id`	No
`product_id`	No
`checkout_id`	Yes
`total_cents`	Yes
`product_name`	No
`claims_summary`	No	Inspection is 3 days after the buyer marks the order received. Short-unit claims apply beyond a 5% tolerance. Salvage is as-is. Not-received claims are allowed while the order is shipped.
`shipping_cents`	No
`subtotal_cents`	No
`buyer_fee_cents`	No
`seller_of_record`	Yes
`unit_price_cents`	No
`claims_policy_url`	No
`confirmation_token`	No
`seller_fee_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026
- addedOutput schema / properties / confirmation_token
```
Added value: +{
+  "type": "string"
+}
```

Changed4 schema fields changedNov 9, 2026

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: -"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.",
+  "type": "string"
+}

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds genuinely useful behavior beyond the annotations: no card is charged, buyer read access is required, sign-in is required, and the OAuth discovery endpoint and scope are given. The only weakness is that access requirements are stated twice in slightly different words rather than adding a new fact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short, front-loaded with the capability, with the downstream handoff to confirm_purchase placed before the auth logistics. Some waste in the duplicated 'Requires buyer read access' / 'Requires sign-in with buyer access' phrasing.

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?

An output schema exists, so return values needn't be re-explained, and auth, safety profile (no charge), and next-step routing are all covered. Adequate for a preview tool whose remaining risk is low.

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%, including alias handling for product_id and the 24-hour idempotency_key semantics, so the schema does the heavy lifting. The description adds nothing about quantity, product_id, or idempotency_key, 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?

Names a specific verb (read) plus the exact resources returned — seller of record, unit price, shipping, tax, total — scoped to an instant-checkout listing. 'Does not charge a card' plus the pointer to confirm_purchase separates it from the adjacent write/payment tools in the sibling list.

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?

Establishes the workflow context clearly: preview first, then hand the returned checkout_id to confirm_purchase. It also states the required access level. It stops short of explicit exclusions (e.g., when to use quick_buy instead), so it is short of a 5.

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?