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.2/5.0

Behavior4/5

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

With annotations supplied, the description still adds real value beyond them by disclosing a hard rate limit (5 anonymous quotes per hour per IP) and the credential model for binding a quote to an account. The mutation character is already covered by readOnlyHint=false and idempotentHint=false, so the remaining gap is only the practical consequence of duplicate submissions.

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?

Three tight sentences with no filler. The core action is front-loaded, followed by the required credential field, then the rate limit and token alternative — each sentence carries distinct, load-bearing information.

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

Completeness5/5

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

For a 7-parameter mutation with full schema descriptions and an output schema, the description covers the gaps structured data can't: auth modes, required reply email, and rate limiting. An agent has everything needed to invoke it correctly without a return-value spec.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining buyer_email's role (required, and the channel the seller replies to) and how X-Agent-Token changes its meaning. That added semantics is genuinely beyond the schema's terse field descriptions.

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 concrete verb+resource ("Request a bulk quote for a product") and scopes it with "(buyer tool)," which separates it from seller-side siblings like respond_to_quote and get_quote_requests. It does not name the alternative tools an agent might reach for, so the differentiation is implied rather than explicit.

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?

It clearly explains the two operating modes and when each applies: anonymous use (no credentials, buyer_email mandatory as the reply channel) versus an X-Agent-Token that binds the quote to a buyer account. What's missing is routing guidance against siblings such as get_quote_status or quick_buy, so it gives context but no exclusions.

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?