ForthClear Liquidation Marketplace

Mark order received

mark_order_received

DestructiveIdempotent

Mark a shipped order received. This starts the 3-day inspection window and does not pay the seller. 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": "mark_order_received"
  }
}

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
`status`	Yes
`order_id`	Yes
`inspection_deadline`	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?

Adds real context beyond the annotations: it discloses the 3-day inspection window, that the seller is not paid, and the required buyer write scope with the OAuth discovery endpoint. It does not explain why destructiveHint is true (e.g. whether the action can be undone), which is the one behavioral gap left.

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?

Front-loaded with the action and its consequence, then auth requirements. Slightly redundant with 'Requires buyer write access. Requires sign-in with buyer access.' restating the same constraint twice.

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?

An output schema exists so return values need not be described, and auth/scope requirements are covered. For a two-parameter state-transition tool this is nearly complete, missing only a note on reversibility given the destructive hint.

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 both order_id and idempotency_key are already fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 and resource ('Mark a shipped order received') and names the resulting state transition (3-day inspection window). It is distinguishable from siblings like confirm_order or accept_quote_and_pay, though it never explicitly contrasts itself with them.

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 'shipped order' implies the precondition that the order must already be in shipped state, and 'does not pay the seller' hints at when this is not the payment step. However, no alternative tool is named and no explicit when-not guidance is given.

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?