ForthClear Liquidation Marketplace

Cancel overdue unshipped order

cancel_order

DestructiveIdempotent

Cancel an unshipped order whose ship-by date has passed, for a full refund. Seller Agreement §5.4. 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": {
      "order_id": "<order_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "cancel_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
`refund`	No
`status`	Yes
`is_test`	No
`order_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already flag destructiveHint and idempotentHint, and the description goes well beyond them: it names the refund consequence, cites Seller Agreement §5.4, discloses the buyer purchase access requirement, points to the OAuth discovery endpoint and buyer:purchase scope, and warns that per-call user approval is required. That is exactly the context an agent needs before a destructive mutation.

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 core purpose and its conditions are front-loaded in the first sentence, and every following sentence carries real information (legal basis, auth, approval). The telegraphic fragment style around the OAuth discovery URL is slightly choppy but not wasteful.

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?

For a destructive two-parameter mutation with an output schema, the description covers preconditions, side effect (refund), authorization, and approval requirements. The only minor gap is what happens when the order does not meet the preconditions or what to do instead.

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 order_id and idempotency_key semantics (including the 24-hour replay window) are already fully documented in the schema. The description adds no additional meaning about either parameter, so the baseline applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (cancel), resource (order), and precise qualifying conditions (unshipped, ship-by date passed), plus the outcome (full refund). No sibling tool cancels orders, so an agent can distinguish it from get_order_status, open_dispute, or bulk_mark_shipped without opening the schema.

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?

The preconditions for use are explicit: the order must be unshipped and past its ship-by date. This effectively rules out shipped or in-transit orders, but it does not name a fallback path for those cases (e.g., open_dispute), leaving the agent to infer alternatives.

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?