ForthClear Liquidation Marketplace

Request a bulk quote

request_quote

Request a bulk quote for a product (buyer tool)

Input Schema

TableJSON Schema

Name	Required	Description
`message`	No	Additional message to seller
`quantity`	Yes	Number of units to quote
`buyer_name`	No	Buyer's full name
`product_id`	Yes	Product ID (format: product_123)
`buyer_email`	Yes	Buyer's email address (required)
`target_price`	No	Target price per unit in cents (optional)
`buyer_company`	No	Buyer's company name

Output Schema

TableJSON Schema

Name	Required	Description	Default
`quote`	Yes
`message`	Yes
`success`	Yes

Schema Changelog

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

Changed1 schema field changedAug 30, 2026

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

First observedAug 21, 2026

TDQS

B3.4/5.0

Behavior2/5

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

The description adds no behavioral details beyond the annotations. It does not say that a quote request record is created, that the seller is notified, that it is non-idempotent, or anything about scope or side effects. Annotations already signal mutation, but the description itself contributes no extra behavioral transparency.

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 extremely concise and front-loaded with the core action. The '(buyer tool)' parenthetical adds genuinely useful contextual information. It loses one point because the main clause largely restates the title, but there is no wasteful or extraneous content.

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?

For a relatively simple action with a fully documented schema, the description is minimally adequate. It covers what the tool does and who it is for. However, it leaves usage alternatives and behavioral outcomes unstated, which an agent may need when deciding between request_quote, quick_buy, and quote-related sibling 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 description coverage is 100%, so the parameter definitions already document product_id, quantity, buyer_email, and optional fields. The description adds no param-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb ('request'), a clear resource ('a bulk quote for a product'), and a critical contextual tag ('buyer tool'). This distinguishes it from seller-facing siblings like respond_to_quote and get_quote_requests, and the 'bulk' qualifier separates it from quick_buy.

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 phrase '(buyer tool)' implies this is for buyer-initiated quote requests, and 'bulk' implies it is for bulk purchasing rather than quick single purchases. However, there is no explicit when-to-use guidance, no mention of alternatives, and no warning not to use it for seller-side quote actions.

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?