cross-review

Start Until Unanimous

session_start_unanimous

Start background API generation/revision rounds across AI peers, continuing until unanimous agreement, max rounds, or budget limit. Evidence persists and transports automatically.

Instructions

Start real API generation/revision rounds in the background until unanimity, max_rounds or budget limit. AI evidence supplied in evidence is persisted durably and transported automatically; no separate attachment step is required. v2.11.0: same caller + relator-lottery semantics as run_until_unanimous — see that tool for details. When session_id names an existing session, requires the verified capability token of that session's persisted petitioner; opening a new session does not.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No		ship
`task`	Yes
`peers`	No
`caller`	Yes
`evidence`	No	Raw evidence from the authenticated AI caller. It is persisted automatically as durable, SHA-256-addressed caller_submitted_unverified material and transported to reviewers. This is the routine path; `session_attach_evidence` attaches the same material out of band and grants it no additional provenance.
`lead_peer`	No
`max_rounds`	No	Hard review-round ceiling unless allow_auto_extension is explicitly true.
`session_id`	No
`max_cost_usd`	No
`review_focus`	No	Optional provider-neutral review scope anchor. This is not Claude Code's /focus UI command; it is injected as a front-loaded Review Focus prompt block for every selected peer, including OUT OF SCOPE handling for unrelated findings.
`initial_draft`	No
`until_stopped`	No
`response_format`	No		json
`allow_auto_extension`	No	Opt in to at most two evidence-only auto-extensions. False keeps max_rounds rigid.
`reasoning_effort_overrides`	No	Optional per-peer reasoning_effort overrides for this call. Keys are peer ids (codex\|claude\|gemini\|deepseek\|grok\|perplexity); missing keys fall back to global config. This is a shared scale: adapters normalize unsupported literals to the selected model's documented enum (`ultra` becomes max on GPT-6 Astra, GPT-5.6, Kimi K3 via Perplexity and DeepSeek, and xhigh on Grok 4.6; older GPT-5 families use their own ceilings).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv4.4.18Sep 17, 2026

removedInput schema / properties / caller / default
```
Removed value: -"operator"
```

changedInput schema / properties / caller / enum

Previous value: -[
-  "codex",
-  "claude",
-  "gemini",
-  "deepseek",
-  "grok",
-  "perplexity",
-  "operator"
-]New value: +[
+  "codex",
+  "claude",
+  "gemini",
+  "deepseek",
+  "grok",
+  "perplexity"
+]

changedInput schema / properties / evidence / description

Previous value: -"Raw evidence from the authenticated AI caller. It is persisted automatically as durable, SHA-256-addressed caller_submitted_unverified material and transported to reviewers; no manual operator attachment is required. Do not call session_attach_evidence for this routine path."New value: +"Raw evidence from the authenticated AI caller. It is persisted automatically as durable, SHA-256-addressed caller_submitted_unverified material and transported to reviewers. This is the routine path; `session_attach_evidence` attaches the same material out of band and grants it no additional provenance."

changedInput schema / properties / reasoning_effort_overrides / description

Previous value: -"Optional per-peer reasoning_effort overrides for this call. Keys are peer ids (codex|claude|gemini|deepseek|grok|perplexity); missing keys fall back to global config. This is a shared scale: adapters normalize unsupported literals to the selected model's documented enum (`ultra` becomes max on GPT-5.6, Kimi K3 via Perplexity and DeepSeek, and xhigh on Grok 4.6; older GPT-5 families use their own ceilings)."New value: +"Optional per-peer reasoning_effort overrides for this call. Keys are peer ids (codex|claude|gemini|deepseek|grok|perplexity); missing keys fall back to global config. This is a shared scale: adapters normalize unsupported literals to the selected model's documented enum (`ultra` becomes max on GPT-6 Astra, GPT-5.6, Kimi K3 via Perplexity and DeepSeek, and xhigh on Grok 4.6; older GPT-5 families use their own ceilings)."

changedInput schema / required

Previous value: -[
-  "task"
-]New value: +[
+  "task",
+  "caller"
+]

Changed1 schema field changedv4.4.13Aug 26, 2026

changedInput schema / properties / reasoning_effort_overrides / description

Previous value: -"Optional per-peer reasoning_effort overrides for this call. Keys are peer ids (codex|claude|gemini|deepseek|grok|perplexity); missing keys fall back to global config. This is a shared scale: adapters normalize unsupported literals to the selected model's documented enum (`ultra` becomes max on GPT-5.6 and high on Grok 4.5; older GPT-5 families use their own ceilings)."New value: +"Optional per-peer reasoning_effort overrides for this call. Keys are peer ids (codex|claude|gemini|deepseek|grok|perplexity); missing keys fall back to global config. This is a shared scale: adapters normalize unsupported literals to the selected model's documented enum (`ultra` becomes max on GPT-5.6, Kimi K3 via Perplexity and DeepSeek, and xhigh on Grok 4.6; older GPT-5 families use their own ceilings)."

Changed10 schema fields changedv4.4.9Jul 14, 2026

addedInput schema / properties / allow_auto_extension

Added value: +{
+  "default": false,
+  "description": "Opt in to at most two evidence-only auto-extensions. False keeps max_rounds rigid.",
+  "type": "boolean"
+}

addedInput schema / properties / evidence / description

Added value: +"Raw evidence from the authenticated AI caller. It is persisted automatically as durable, SHA-256-addressed caller_submitted_unverified material and transported to reviewers; no manual operator attachment is required. Do not call session_attach_evidence for this routine path."

addedInput schema / properties / max_rounds / description

Added value: +"Hard review-round ceiling unless allow_auto_extension is explicitly true."

changedInput schema / properties / reasoning_effort_overrides / description

Previous value: -"Optional per-peer reasoning_effort overrides for this call. Keys are peer ids (codex|claude|gemini|deepseek|grok|perplexity); missing keys fall back to global config. Useful to dial down expensive peers (e.g. Grok grok-4.20-multi-agent xhigh = 16 agents, or Perplexity sonar-deep-research that bills citation + reasoning + search queries separately) for routine reviews without editing the host MCP configs."New value: +"Optional per-peer reasoning_effort overrides for this call. Keys are peer ids (codex|claude|gemini|deepseek|grok|perplexity); missing keys fall back to global config. This is a shared scale: adapters normalize unsupported literals to the selected model's documented enum (`ultra` becomes max on GPT-5.6 and high on Grok 4.5; older GPT-5 families use their own ceilings)."

changedInput schema / properties / reasoning_effort_overrides / properties / claude / enum

Previous value: -[
-  "none",
-  "minimal",
-  "low",
-  "medium",
-  "high",
-  "xhigh",
-  "max"
-]New value: +[
+  "none",
+  "minimal",
+  "low",
+  "medium",
+  "high",
+  "xhigh",
+  "max",
+  "ultra"
+]

changedInput schema / properties / reasoning_effort_overrides / properties / codex / enum

Previous value: -[
-  "none",
-  "minimal",
-  "low",
-  "medium",
-  "high",
-  "xhigh",
-  "max"
-]New value: +[
+  "none",
+  "minimal",
+  "low",
+  "medium",
+  "high",
+  "xhigh",
+  "max",
+  "ultra"
+]

changedInput schema / properties / reasoning_effort_overrides / properties / deepseek / enum

Previous value: -[
-  "none",
-  "minimal",
-  "low",
-  "medium",
-  "high",
-  "xhigh",
-  "max"
-]New value: +[
+  "none",
+  "minimal",
+  "low",
+  "medium",
+  "high",
+  "xhigh",
+  "max",
+  "ultra"
+]

changedInput schema / properties / reasoning_effort_overrides / properties / gemini / enum

Previous value: -[
-  "none",
-  "minimal",
-  "low",
-  "medium",
-  "high",
-  "xhigh",
-  "max"
-]New value: +[
+  "none",
+  "minimal",
+  "low",
+  "medium",
+  "high",
+  "xhigh",
+  "max",
+  "ultra"
+]

changedInput schema / properties / reasoning_effort_overrides / properties / grok / enum

Previous value: -[
-  "none",
-  "minimal",
-  "low",
-  "medium",
-  "high",
-  "xhigh",
-  "max"
-]New value: +[
+  "none",
+  "minimal",
+  "low",
+  "medium",
+  "high",
+  "xhigh",
+  "max",
+  "ultra"
+]

changedInput schema / properties / reasoning_effort_overrides / properties / perplexity / enum

Previous value: -[
-  "none",
-  "minimal",
-  "low",
-  "medium",
-  "high",
-  "xhigh",
-  "max"
-]New value: +[
+  "none",
+  "minimal",
+  "low",
+  "medium",
+  "high",
+  "xhigh",
+  "max",
+  "ultra"
+]

First observedv4.4.8Jul 4, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds meaningful behavioral detail beyond the annotations: background/asynchronous execution, durable persistence of evidence, automatic transport to reviewers, and a token requirement for existing sessions. This is consistent with annotations declaring readOnly=false and idempotent=false, and it gives the agent a clearer picture of side effects and prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-organized: the first sentence states the core purpose, the second covers evidence behavior, the third points to sibling semantics, and the fourth addresses session security. There is little wasted text, and important information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex 15-parameter background job with no output schema, yet the description does not explain the return value, how to monitor progress, or how parameters such as task, mode, peers, and lead_peer interact. Delegating key semantics to run_until_unanimous helps, but the definition is not self-sufficient for an agent trying to invoke it correctly in diverse situations.

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?

The description adds semantics for key parameters: evidence is persisted durably, session_id has a token requirement, caller semantics are delegated to run_until_unanimous, and termination depends on max_rounds or budget. However, schema description coverage is only 33%, and the description still leaves many parameters — such as task, mode, peers, lead_peer, initial_draft, and response_format — without meaningful explanation.

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?

The description opens with a specific action and resource: starting real API generation/revision rounds in the background. It states termination conditions (unanimity, max_rounds, or budget limit) and distinguishes itself from siblings by emphasizing background execution and referencing run_until_unanimous. This is sufficient for an agent to identify what the tool does and how it differs from session_start_round.

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 description provides clear context: uses background rounds, persists evidence automatically so no separate attachment step is needed, and explains the capability-token requirement when resuming an existing session. It does not fully articulate when not to use this tool versus other siblings, but the context is clear enough for most selection decisions.

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

Start Until Unanimous

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools