Skip to main content
Glama

ForthClear Liquidation Marketplace

Request a bulk quote

request_quote
Idempotent

Ask a seller to price a bulk order. No sign-in required if you pass buyer_email, which is where the seller replies. buyer_email is always required, including when you are signed in. Anonymous requests are limited to 5 per hour. Sign in with buyer access to attach the quote to your account. Save status_token and pass it to get_quote_status. This does not charge a card. 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": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias for product_id.
slugNoAlias for product_id. Public listing slug.
messageNoAdditional message to seller
quantityYesNumber of units to quote
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 (required)
target_priceNoTarget price per unit in cents (optional)
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
quoteYes
messageYes
successYes
status_tokenNoPass to get_quote_status to read this quote back. Keep it: an anonymous caller has no other way in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. 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 / properties / quote / properties / expected_response / description
      Previous value: -"Human-readable SLA, e.g. \"24-48 hours\"."New value: +"What happens next. The seller is notified. There is no guaranteed reply time."
  3. Changed1 schema field changed
    • addedOutput schema / properties / status_token
      Added value: +{
      +  "description": "Pass to get_quote_status to read this quote back. Keep it: an anonymous caller has no other way in.",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "type": "string"
      +    },
      +    "quote": {
      +      "properties": {
      +        "expected_response": {
      +          "description": "Human-readable SLA, e.g. \"24-48 hours\".",
      +          "type": "string"
      +        },
      +        "id": {
      +          "type": "integer"
      +        },
      +        "product_id": {
      +          "type": "string"
      +        },
      +        "product_name": {
      +          "type": "string"
      +        },
      +        "quantity": {
      +          "type": "integer"
      +        },
      +        "seller_company": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "type": "string"
      +        },
      +        "target_price": {
      +          "description": "Buyer target per unit, as supplied.",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "product_id",
      +        "product_name",
      +        "quantity",
      +        "status",
      +        "expected_response"
      +      ],
      +      "type": "object"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "message",
      +    "quote"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the anonymous rate limit (5/hour), the auth model (buyer_email required even when signed in), what signing in changes (quote attaches to account), the need to persist status_token, and that no card is charged. It also flags a user-approval requirement per call, which no annotation conveys.

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 sentences that each carry information: purpose, auth path, rate limit, follow-up, billing, approval. The sign-in/buyer_email point is stated twice in slightly different words, which is mildly redundant but aids clarity rather than bloating the text.

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, open-world, approval-gated tool this covers everything an agent needs before calling: auth requirements, rate limits, idempotency expectations (via the schema), billing safety, and the handoff token for status checks. An output schema exists, so return-shape detail is correctly omitted.

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 adds genuine meaning by explaining that buyer_email is the reply channel and remains required regardless of sign-in state. It also introduces status_token as a returned value to carry into get_quote_status, which the input schema alone does not surface.

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?

States a specific verb and resource ('Ask a seller to price a bulk order') and implicitly contrasts with the transactional siblings by noting 'This does not charge a card.' An agent can distinguish this from accept_quote_and_pay or quick_buy without opening either schema.

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?

Gives clear operational context (anonymous vs. signed-in path) and explicitly routes follow-up to get_quote_status. It does not explicitly name when to prefer quick_buy or preview_checkout over requesting a quote, so there is a small gap in alternative selection, but the bulk-vs-purchase framing covers most of it.

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