proxy-shopping

Countersign the ruling

countersign_ruling

Destructive

Add your signature to the escrow's ruling transaction and broadcast it to settle a dispute; previews unless confirm is true.

Instructions

Moves money: add your signature to the escrow's ruling transaction (2 of 3) and broadcast it, settling the dispute. Refused if the transaction does not pay the ruled split. Without confirm: true it returns the same review as review_ruling. Ask your human before confirming.

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>"
    },
    "name": "countersign_ruling"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	true to really do it (sign / send / broadcast); omitted or false = preview only, nothing happens
`order_id`	Yes	order id (32 hex characters) from request_quote or list_orders

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false. The description adds real value beyond them: it specifies that money moves and the dispute is settled, the refusal condition, and the confirm-gated preview behavior — context an agent cannot get from the annotations alone.

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-loads the critical fact ('Moves money') and packs the precondition, preview behavior, and safety directive into a compact block. Dense but every clause earns its place; slightly clausal but no fluff.

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?

No output schema exists, but the description explains the return behavior (returns the same review as review_ruling when not confirmed) and the main failure mode. Combined with destructive annotations, an agent has enough to invoke it safely; only exhaustiveness of error cases is unstated.

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% and the schema already documents both confirm (preview vs real) and order_id (32-hex from request_quote/list_orders). The description reinforces the confirm semantics but adds little beyond the schema, so the baseline 3 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 (countersign/sign+broadcast) and resource (the escrow's ruling transaction), plus the concrete effect — 'Moves money' and 'settling the dispute'. It implicitly distinguishes itself from review_ruling by naming it as the fallback behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions ('Refused if the transaction does not pay the ruled split'), the preview-vs-execute condition ('Without confirm: true it returns the same review as review_ruling'), and a human-in-the-loop directive ('Ask your human before confirming'). This is close to a full when/when-not/guardrail set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.