Skip to main content
Glama

ForthClear Liquidation Marketplace

Quick buy

quick_buy
DestructiveIdempotent

Price an instant checkout for one listing. This does not charge the card. When the signed-in buyer has a saved card and the total is under US$1,000, the result is a summary (items, shipping, total, seller) plus a confirmation_token. Call confirm_purchase with that token and payment.saved_card true to charge the saved card. If there is no saved card, or the card needs authentication (including charges of US$1,000 or more), the result includes the existing checkout link instead. The listing's seller sells the goods. ForthClear runs the marketplace and Stripe processes the payment. buyer_email is required. quantity must be a positive integer below the listing's quote threshold (quote_quantity_threshold from get_product_details). A threshold of 1 means no quantity can be bought instantly. Use request_quote. The listing must have instant checkout and a shipping price. Requires sign-in with buyer access. OAuth discovery: /.well-known/oauth-authorization-server (scope buyer:purchase). Sensitive: requires user approval each time.

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>",
      "buyer_email": "<buyer_email>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "quick_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias for product_id.
slugNoAlias for product_id. Public listing slug.
quantityYesNumber of units to purchase
productIdNoAlias for product_id.
buyer_nameNoBuyer's full name
product_idYesExact id from search, for example product_2731. productId, id, and slug are aliases.
buyer_emailYesBuyer's email address
buyer_companyNoBuyer's company name
idempotency_keyYesRequired. 8–200 characters (letters, digits, . _ : -). The same key returns the original result for 24 hours and is sent to Stripe as Idempotency-Key.

Output Schema

NameRequiredDescriptionDefault
itemsNo
is_testNo
messageNo
paymentYes
successYes
checkoutYes
next_stepsYes
total_centsNo
add_card_urlNo
shipping_centsNo
fallback_reasonNo
seller_of_recordNo
confirmation_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • addedOutput schema / properties / add_card_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / checkout / properties / confirmation_token
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / checkout / properties / is_test
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / checkout / properties / seller_of_record
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / checkout / properties / shipping
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / confirmation_token
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / fallback_reason
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / is_test
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / items
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "product_id": {
      +        "type": "string"
      +      },
      +      "quantity": {
      +        "type": "integer"
      +      },
      +      "unit_price_cents": {
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "product_id",
      +      "quantity",
      +      "unit_price_cents"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / payment / properties / add_card_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / payment / properties / checkout_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / payment / properties / confirmation_token
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / payment / properties / next_tool
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / payment / properties / requires_confirmation
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / seller_of_record
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / shipping_cents
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / total_cents
      Added value: +{
      +  "type": "integer"
      +}
  2. Changed4 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: -"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"
      +}
  3. Changed4 schema fields changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Required. 8–200 characters (letters, digits, . _ : -). The same key returns the original result for 24 hours and is sent to Stripe as Idempotency-Key.",
      +  "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"
    • changedInput schema / required
      Previous value: -[
      -  "product_id",
      -  "quantity",
      -  "buyer_email"
      -]New value: +[
      +  "product_id",
      +  "quantity",
      +  "buyer_email",
      +  "idempotency_key"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkout": {
      +      "properties": {
      +        "currency": {
      +          "type": "string"
      +        },
      +        "grand_total": {
      +          "type": "integer"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "platform_fee": {
      +          "type": "integer"
      +        },
      +        "product_name": {
      +          "type": "string"
      +        },
      +        "quantity": {
      +          "type": "integer"
      +        },
      +        "status": {
      +          "type": "string"
      +        },
      +        "subtotal": {
      +          "type": "integer"
      +        },
      +        "unit_price": {
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "status",
      +        "quantity",
      +        "grand_total"
      +      ],
      +      "type": "object"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "next_steps": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "payment": {
      +      "properties": {
      +        "complete_url": {
      +          "type": "string"
      +        },
      +        "contact_url": {
      +          "type": "string"
      +        },
      +        "instructions": {
      +          "type": "string"
      +        },
      +        "method": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "method",
      +        "instructions"
      +      ],
      +      "type": "object"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "checkout",
      +    "payment",
      +    "next_steps"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • removedInput schema / properties / shipping_country
      Removed value: -{
      -  "description": "Two-letter country code (e.g., US, GB)",
      -  "type": "string"
      -}
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructive/openWorld/idempotent, and the description adds real value on top: no charge occurs, the two possible result shapes, the US$1,000 auth boundary, sign-in scope buyer:purchase, and per-call user approval. The only gap is it doesn't restate idempotency behavior, which the schema already covers.

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?

Front-loaded with the key outcome (price, no charge) and the follow-up action. Some sentences are choppy and loosely ordered near the end ('The listing's seller sells the goods', 'buyer_email is required') but nearly all carry substantive constraints.

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?

For a mutating, OAuth-gated purchase step, the description covers preconditions (instant checkout enabled, shipping price present, saved card, threshold), both outcome branches, and the exact next call. Return values are also backed by an output schema, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns extra by explaining that buyer_email is required, that quantity must be a positive integer below quote_quantity_threshold, and that a threshold of 1 disables instant purchase entirely — meaning not visible in the schema.

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?

Opens with a specific verb and resource — 'Price an instant checkout for one listing' — and immediately negates the most likely misinterpretation ('This does not charge the card'), which cleanly separates it from confirm_purchase.

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

Usage Guidelines5/5

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

Gives explicit branching: call this to price and obtain a confirmation_token, then call confirm_purchase with that token; use request_quote when quantity meets the quote threshold, and use the checkout link when no saved card exists or authentication is needed. Alternatives and exclusion conditions are both named.

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