ForthClear Liquidation Marketplace

Request a bulk quote

request_quote

Request a bulk quote for a product (buyer tool). Works without credentials: buyer_email is required and is where the seller replies. Anonymous quotes are limited to 5 per hour per IP; a buyer X-Agent-Token binds the quote to the buyer's account instead.

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
`quote`	Yes
`message`	Yes
`success`	Yes
`status_token`	No	Pass 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.

Changed1 schema field changedSep 27, 2026

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

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

A4/5.0

Behavior4/5

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

Annotations already declare non-read-only, open-world and non-idempotent behavior. The description adds genuinely new operational context beyond that: the 5-per-hour-per-IP anonymous rate limit, the credential-free path, and where the seller's reply is delivered.

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?

Two tight sentences with no filler; the core action and the keyword-level usage constraints are front-loaded in the first clause, and nothing repeats the schema.

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?

With annotations covering the safety profile and an output schema covering return values, the description supplies the missing pieces an agent needs (auth paths and rate limit). Minor gap: no guidance on failure behavior when the anonymous quota is exhausted.

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 schema already documents all seven parameters and their formats. The description adds only that buyer_email is required and serves as the reply address, which is useful but marginal against a fully documented schema.

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?

States a specific verb+resource ('Request a bulk quote for a product') and tags itself as a buyer-side tool, which distinguishes it from seller-side siblings like respond_to_quote and get_quote_requests. It does not name an alternative explicitly, so it falls short of a 5.

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?

Explains the credential model clearly: works without credentials, buyer_email is required as the reply destination, and a buyer X-Agent-Token binds the quote to an account. It gives conditions for use but never says when to prefer this over siblings such as get_quote_status or respond_to_quote.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?