Skip to main content
Glama

ForthClear Liquidation Marketplace

Get pricing recommendation

get_pricing_recommendation
Read-only

Suggest a liquidation unit price in cents from MSRP, condition, category, and lot size. No sign-in required. original_retail is MSRP per unit in cents. Larger lots suggest a lower per-unit price. The result is bounded below retail. This does not change any listing's price.

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": {
      "category": "<category>",
      "condition": "<condition>",
      "original_retail": "<original_retail>"
    },
    "name": "get_pricing_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesCatalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other.
quantityNoUnits in the lot. Larger lots get a lower per-unit suggestion. Omit for a small lot.
conditionYesCondition of the goods: salvage (sold as-is), customer returns, shelf pulls, overstock, or new or refurbished.
original_retailYesMSRP per unit in cents. 5000 means $50.00. Required, and must be greater than zero.

Output Schema

NameRequiredDescriptionDefault
tipsYes
factorsYes
price_rangeYes
recommended_priceYes
discount_from_retailYesPercent below original retail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / original_retail / description
      Previous value: -"Original retail price in cents"New value: +"MSRP per unit in cents. 5000 means $50.00. Required, and must be greater than zero."
    • changedInput schema / properties / quantity / description
      Previous value: -"Lot size being priced; recommendations scale with volume."New value: +"Units in the lot. Larger lots get a lower per-unit suggestion. Omit for a small lot."
  2. Changed1 schema field changed
    • changedInput schema / properties / condition / description
      Previous value: -"Standard liquidation condition grade (Task #72)"New value: +"Condition of the goods: salvage (sold as-is), customer returns, shelf pulls, overstock, or new or refurbished."
  3. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Catalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other."
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "electronics",
      +  "apparel",
      +  "home_goods",
      +  "beauty",
      +  "sports",
      +  "kitchenware",
      +  "office_supplies",
      +  "toys",
      +  "food_beverage",
      +  "tools",
      +  "other"
      +]
    • addedInput schema / properties / quantity / description
      Added value: +"Lot size being priced; recommendations scale with volume."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "discount_from_retail": {
      +      "description": "Percent below original retail.",
      +      "type": "number"
      +    },
      +    "factors": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "price_range": {
      +      "properties": {
      +        "high": {
      +          "type": "number"
      +        },
      +        "low": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "low",
      +        "high"
      +      ],
      +      "type": "object"
      +    },
      +    "recommended_price": {
      +      "type": "number"
      +    },
      +    "tips": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "recommended_price",
      +    "price_range",
      +    "discount_from_retail",
      +    "factors",
      +    "tips"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.1/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 the safety profile is covered; the description still adds real behavior: auth-free access, the inverse relationship between lot size and per-unit price, and the guarantee the result is bounded below retail. These are pricing-model traits the agent cannot get from the annotation block.

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?

Five short sentences, front-loaded with the purpose and the unit convention. Minor waste: 'original_retail is MSRP per unit in cents' duplicates the schema field description almost verbatim.

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 shape need not be explained; the description covers inputs, the cents convention, auth, and the non-mutating guarantee. Only the optional-quantity default and the meaning of the bounds relative to condition are left implicit, which is a small gap.

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 coverage is 100% and the schema already documents cents-vs-dollars for original_retail, the lot-size effect on quantity, and all enum values. The description restates 'original_retail is MSRP per unit in cents' and the larger-lot behavior, so it adds little beyond the schema, warranting the baseline 3.

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 ('Suggest a liquidation unit price') plus the exact inputs that drive it (MSRP, condition, category, lot size). No sibling tool offers pricing advice, so an agent can distinguish this from get_product_details or create_listing without opening a 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?

'No sign-in required' establishes a concrete precondition for calling it, and 'This does not change any listing's price' frames it as advisory rather than a listing update. It stops short of naming alternatives or stating when-not to use it, but the usage context is clear.

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