ForthClear Liquidation Marketplace

Search inventory

search_inventory

Read-only

Search available liquidation inventory with filters

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum listings to return (default 20, max 100).
`query`	No	Search query
`category`	No	Product category
`condition`	No	Standard liquidation condition grade (Task #72)
`max_price`	No	Maximum price in cents

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes	Catalogue matches before the limit is applied.
`message`	Yes
`products`	Yes

Schema Changelog

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

Changed3 schema fields changedAug 29, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum listings to return (default 20, max 100)."

removedInput schema / properties / min_discount

Removed value: -{
-  "maximum": 100,
-  "minimum": 0,
-  "type": "integer"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "products": {
+      "items": {
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "condition": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "discount_percent": {
+            "description": "Null when the listing has no original retail price on file.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Opaque listing id, `product_<n>`.",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "price": {
+            "description": "Unit price in cents.",
+            "type": "integer"
+          },
+          "quantity": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "category",
+          "quantity",
+          "price"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Catalogue matches before the limit is applied.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "products",
+    "total",
+    "message"
+  ],
+  "type": "object"
+}

First observedAug 21, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the notion of 'available' inventory but doesn't disclose return behavior, sorting, or that all parameters are optional filters. With annotation coverage, this is adequate but not rich.

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?

The description is one sentence, front-loaded with the core action, and contains no filler. 'with filters' is slightly generic but doesn't waste words; it could have been more informative without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a fully described schema and an output schema, and annotations cover safety, so the gaps are mostly around usage guidance and sibling differentiation. An agent can reasonably infer how to call it, but not when to prefer it over related read tools.

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%; each parameter already has a description including default/max for limit and the enum for condition. The description's generic 'with filters' adds no parameter-specific meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Search') and resource ('available liquidation inventory'), and mentions filters. It doesn't explicitly differentiate from sibling read tools like get_product_details, but the verb 'search' implies a list/scoped query rather than a single-item lookup.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool vs alternatives, or when to use a sibling like get_product_details for individual item lookups. The description is a bare directive with no exclusions or context.

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?