From 85e2662bdd2dbe4552a063c9c0fe239490384e7a Mon Sep 17 00:00:00 2001 From: mobee-multiharness Date: Mon, 27 Jul 2026 17:00:13 -0700 Subject: [PATCH] mcp: the harness field is a hard award filter, not a recorded preference MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The schema description still said harness was "not yet a hard filter (no claim wire field carries it)" after the multi-harness slice made it exactly that. This is the one string an LLM buyer reads to decide whether the field does anything, so it was telling the reader who acts on it the opposite of the truth — a buyer would reasonably drop the field as decorative. The sibling model field's identical caveat is left alone: it is still true. Co-Authored-By: Claude Opus 5 --- crates/mobee/src/mcp.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/mobee/src/mcp.rs b/crates/mobee/src/mcp.rs index bf5c4757..38394d00 100644 --- a/crates/mobee/src/mcp.rs +++ b/crates/mobee/src/mcp.rs @@ -175,7 +175,7 @@ fn tools() -> Value { }, "harness": { "type": "string", - "description": "Preferred seller harness (e.g. claude|cursor|codex). Recorded as an auto-award preference; not yet a hard filter (no claim wire field carries it)." + "description": "Request a specific seller harness (e.g. claude|cursor|codex). Posted on the offer as [\"param\",\"agent\",] and enforced as a HARD award filter: only a seller advertising that harness on its claim can be awarded, and a seller that cannot run it will not claim at all. Omit it (or pass \"any\") for no preference. Also recorded as the auto-award preference it always was." }, "model": { "type": "string",