ForthClear Liquidation Marketplace

Accept counter and pay

accept_quote_and_pay

DestructiveIdempotent

Accept a seller's quoted price and charge it with the same payment options as confirm_purchase. Requires buyer purchase access. Requires sign-in with buyer access. OAuth discovery: /.well-known/oauth-authorization-server (scope buyer:purchase). Sensitive: requires user approval each time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "quote_id": "<quote_id>",
      "payment": "<payment>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "accept_quote_and_pay"
  }
}

Input Schema

Name	Required	Description
`payment`	Yes	Same payment object as confirm_purchase.
`quote_id`	Yes	Quote id from list_my_quotes or get_quote_status.
`idempotency_key`	Yes	Required. 8–200 characters (letters, digits, . _ : -). The same key returns the original result for 24 hours and is sent to Stripe as Idempotency-Key.

Output Schema

Name	Required	Description	Default
`status`	Yes
`is_test`	No
`currency`	No
`order_id`	No
`action_url`	No
`checkout_id`	No
`amount_charged_cents`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations already declare destructive, idempotent and open-world behavior, and the description adds genuinely new context: per-call user approval is required, and the OAuth discovery endpoint plus buyer:purchase scope are named. It still doesn't say what happens to an expired or already-accepted quote, but the auth and consent disclosure is meaningful value beyond the structured fields.

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 action is front-loaded in the first clause and the remaining sentences are short prerequisite statements. The two consecutive 'requires buyer ... access' sentences are slightly redundant and could be merged, but there is no filler.

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 an output schema present and full parameter documentation, the definition only needs to carry auth, consent and cross-tool semantics, which it does. Edge-case behavior for stale or already-accepted quotes is the remaining gap for a destructive payment operation.

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%, including the payment object, quote_id source and idempotency_key format, so the baseline is 3. The description only reinforces that the payment object matches confirm_purchase and adds nothing about parameter meaning beyond the 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?

The description gives a concrete verb and resource: accept a seller's quoted price and charge it, and it anchors the payment semantics to the sibling confirm_purchase. It does not explicitly contrast with respond_to_quote or explain why one would accept a quote rather than confirm a purchase, so the sibling differentiation is only partial.

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?

It states prerequisites (buyer purchase access, sign-in with buyer scope) rather than when-to-use guidance. There is no statement of when this should be chosen over respond_to_quote or confirm_purchase, though the buyer-access prerequisite implicitly narrows the caller 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

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?