MCP tools: remote-harness-contract

All tool groups

remote-harness-contract

Registered when: platform: harness.contract covering the key's org (off by default) + a valid x-goodqa-run-id request header. Typed result for this run; writes no data.

submit_turn_result

Submit the result of this unattended turn (contract goodqa-turn/1): your reply to the person, every state change you made (with the id each tool returned), the follow-ups to record and anything requiring human approval. Call it ONCE, last. If it answers isError, fix exactly the listed violations and call it again. It writes nothing; the bridge checks every claim against GoodQA.

ParameterTypeRequiredDescription
contractstringyesAlways "goodqa-turn/1".
run_idstringyesThe runId from RUN FACTS, copied exactly.
replystringyesThe message posted to the person, verbatim. Under 1500 characters.
effectsobject[]yesEvery state change this turn made, with the id the tool returned. Never a key you made up.
followupsobject[]yesFollow-ups for the bridge to apply (no operationId: the bridge derives it).
no_followups_reasonstring \nullyes
escalationsobject[]yes
confidence"low" \"medium" \"high"

Example call:

{"name":"submit_turn_result","arguments":{"contract":"<contract>","run_id":"<run_id>","reply":"<reply>","effects":[],"followups":[],"no_followups_reason":"<no_followups_reason>","escalations":[],"confidence":"low"}}

We use essential cookies to keep you signed in. See our Privacy Policy for details.