ForthClear Liquidation Marketplace

Confirm order

confirm_order

DestructiveIdempotent

End the inspection window after it has elapsed. A live order then starts the seller payout. A sandbox order is marked delivered and is not paid out. Requires buyer write access. Requires sign-in with buyer access. OAuth discovery: /.well-known/oauth-authorization-server (scope buyer:write).

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": {
      "order_id": "<order_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "confirm_order"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	Yes	ForthClear order id.
`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
`payout`	No
`status`	Yes
`order_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses the material consequences of the call: a live order begins seller payout and a sandbox order is merely marked delivered. It also states the buyer write access requirement, sign-in requirement, and the OAuth scope plus discovery endpoint. That is richer behavioral context than the annotations alone provide.

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 front-loaded with the core action and outcome branching, then appended with auth details. Every sentence is informative, though the OAuth discovery line is somewhat esoteric. Overall tight and well ordered with minimal waste.

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?

An output schema exists, so return values need not be explained. Given a two-parameter mutation tool, the description covers consequences, environment branching, authorization, and scope, which is sufficient for an agent to call it correctly. Nothing essential is missing.

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%, with order_id and idempotency_key both documented in the schema, including the 24-hour idempotency semantics and Stripe header forwarding. The description adds nothing about parameters, so the baseline of 3 applies since the schema carries the load.

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 action (ending the inspection window) and distinguishes the two outcome branches: a live order triggers seller payout while a sandbox order is marked delivered with no payout. This is concrete and lets an agent understand what confirmation means. It falls short of 5 only because it doesn't explicitly contrast itself with plausible siblings like mark_order_received or cancel_order.

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?

Timing is implied by "after it has elapsed," which tells the agent the window must be over before calling. However, there is no explicit when-to-use versus when-not guidance, no mention of what to do if the window has not elapsed, and no routing to alternative tools such as cancel_order. Usage is implied rather than stated.

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?