ForthClear Liquidation Marketplace

Get pricing recommendation

get_pricing_recommendation

Read-only

Get AI-powered pricing recommendation for inventory (seller tool)

Input Schema

TableJSON Schema

Name	Required	Description
`category`	Yes	Catalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other.
`quantity`	No	Lot size being priced; recommendations scale with volume.
`condition`	Yes	Standard liquidation condition grade (Task #72)
`original_retail`	Yes	Original retail price in cents

Output Schema

TableJSON Schema

Name	Required	Description
`tips`	Yes
`factors`	Yes
`price_range`	Yes
`recommended_price`	Yes
`discount_from_retail`	Yes	Percent below original retail.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedAug 29, 2026

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"
+}

First observedAug 21, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already mark the operation as read-only and non-destructive, so the description does not need to repeat that. It adds that the output is an AI-powered recommendation rather than a guaranteed market price, but it does not discuss response behavior, edge cases, or any additional requirements.

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?

One sentence with no filler; the core action and domain are front-loaded. Every phrase ('AI-powered,' 'pricing recommendation,' 'inventory,' 'seller tool') adds useful targeting information.

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?

For a simple, read-only recommendation tool with full parameter documentation and an output schema, the description is largely sufficient. The only meaningful gap is the absence of explicit usage conditions, but an agent can still identify the tool and invoke it correctly from the structured fields.

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%, so the parameters are already well documented. The description adds no extra meaning about category, condition, quantity, or original_retail beyond that baseline.

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?

The description pairs a specific verb 'Get' with the resource 'pricing recommendation,' scoped to inventory and seller use. This clearly distinguishes the tool from siblings such as search_inventory or get_product_details, which cover different operations and resources.

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

Usage Guidelines3/5

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

The description gives context ('for inventory' and 'seller tool') but no explicit when-to-use or when-not-to-use guidance, and it names no alternative tools. The appropriate usage is implied rather than stated: call this when a seller needs an AI-powered pricing recommendation for inventory.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Most tools target distinct resource/action pairs: search vs details, quote request vs response, bulk export vs bulk ship. The main overlaps are get_quote_requests vs seller_inbox_summarise and quick_buy vs request_quote, but their descriptions provide enough boundary to avoid serious misselection.

Naming Consistency4/5

The majority of tools follow a verb_noun pattern with a clear bulk_ prefix for bulk operations. Minor deviations like quick_buy and seller_inbox_summarise (object before verb) slightly break the pattern, but the naming remains broadly predictable.

Tool Count5/5

12 tools is well within the ideal range for a two-sided marketplace server. Each tool covers a meaningful seller or buyer workflow without feeling redundant or bloated.

Completeness3/5

Core workflows are covered: search, product details, quote negotiation, listing creation, bulk updates, bulk shipping, and export. Notable gaps include no single listing delete/update, no buyer-facing order or quote status tool, and no action to resolve reported issues surfaced by seller_inbox_summarise.

Resources

Need Help?