OMP Tandem

Overview Schema Source Related Servers Discussions Admin

tandem_continue

Start a new goal after completing the previous one by supplying a prompt or turn contract; history and mode persist while old goals and acceptance criteria are reset.

Instructions

Start a NEW current goal after completion; supply exactly one of prompt or turn contract.

History/base policy/mode/cwd persist, but old goals/acceptance do not. The product snapshot stays pinned unless explicitly changed to another revision of the same project. Question timeout is inherited unless explicitly set here. For waiting_input use tandem_reply.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`prompt`	No
`contract`	No
`execution`	No
`review_id`	No
`review_stage`	No
`conversation_id`	Yes
`timeout_seconds`	No
`project_context_id`	No
`question_timeout_seconds`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.3.0Sep 10, 2026

changedInput schema / properties / execution / anyOf

Previous value: -[
-  {
-    "properties": {
-      "model": {
-        "anyOf": [
-          {
-            "minLength": 1,
-            "pattern": "\\S",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      },
-      "profile": {
-        "default": "balanced",
-        "enum": [
-          "quick",
-          "balanced",
-          "deep"
-        ],
-        "type": "string"
-      },
-      "thinking": {
-        "anyOf": [
-          {
-            "enum": [
-              "off",
-              "minimal",
-              "low",
-              "medium",
-              "high",
-              "xhigh",
-              "max"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      },
-      "timeout_seconds": {
-        "anyOf": [
-          {
-            "maximum": 7200,
-            "minimum": 1,
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "model": {
+        "anyOf": [
+          {
+            "minLength": 1,
+            "pattern": "\\S",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      },
+      "profile": {
+        "default": "balanced",
+        "description": "Profile defaults: quick: Defaults to low thinking with a 600-second deadline. balanced: Defaults to high thinking with a 1800-second deadline. deep: Defaults to high thinking with a 3600-second deadline. Uses the same thinking level as balanced with a longer deadline, not higher reasoning. These are default choices; overrides, effective settings, and actual settings are reported separately.",
+        "enum": [
+          "quick",
+          "balanced",
+          "deep"
+        ],
+        "type": "string"
+      },
+      "thinking": {
+        "anyOf": [
+          {
+            "enum": [
+              "off",
+              "minimal",
+              "low",
+              "medium",
+              "high",
+              "xhigh",
+              "max"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      },
+      "timeout_seconds": {
+        "anyOf": [
+          {
+            "maximum": 7200,
+            "minimum": 1,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed8 schema fields changedv3.1.0Sep 9, 2026

addedInput schema / properties / execution

Added value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "model": {
+          "anyOf": [
+            {
+              "minLength": 1,
+              "pattern": "\\S",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "profile": {
+          "default": "balanced",
+          "enum": [
+            "quick",
+            "balanced",
+            "deep"
+          ],
+          "type": "string"
+        },
+        "thinking": {
+          "anyOf": [
+            {
+              "enum": [
+                "off",
+                "minimal",
+                "low",
+                "medium",
+                "high",
+                "xhigh",
+                "max"
+              ],
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "timeout_seconds": {
+          "anyOf": [
+            {
+              "maximum": 7200,
+              "minimum": 1,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / review_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / review_stage

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "independent",
+        "comparison"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / timeout_seconds / anyOf

Added value: +[
+  {
+    "maximum": 7200,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / timeout_seconds / default
```
Previous value: -1800New value: +null
```
removedInput schema / properties / timeout_seconds / maximum
```
Removed value: -7200
```
removedInput schema / properties / timeout_seconds / minimum
```
Removed value: -1
```
removedInput schema / properties / timeout_seconds / type
```
Removed value: -"integer"
```

First observedv3.0.1Sep 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and discloses highly non-obvious state semantics: history/base policy/mode/cwd persist, old goals/acceptance do not, the product snapshot stays pinned unless explicitly changed, and the question timeout is inherited unless overridden. This is exactly the behavioral context an agent needs before invoking a continuation tool.

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?

Around 60 words, with the primary action and the one critical rule in the first sentence, followed by terse, high-value persistence notes. Every sentence earns its place and nothing is redundant.

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 stateful 9-parameter tool with no annotations, the description covers core continuation semantics (what persists, what resets, snapshot pinning, timeout inheritance) and routes the waiting_input case to tandem_reply. It does not explain the optional execution or review-related fields, but the output schema and nested property descriptions cover return values, leaving only a moderate gap.

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 reported at 0%, so the description must compensate; it usefully clarifies the prompt/contract mutual exclusion and timeout inheritance. However, it leaves several parameters (execution, review_id, review_stage, project_context_id) without explanatory text, and the input schema itself supplies most of the remaining structured constraints. The contribution is meaningful but partial.

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 concrete action ('Start a NEW current goal') and the condition 'after completion', which clearly separates it from tandem_start and similar siblings. It also explicitly names tandem_reply for the waiting_input case, so the tool's scope is unmistakable.

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?

It states when to use the tool ('after completion') and gives an explicit exclusion ('For waiting_input use tandem_reply'). It also imposes the critical selection rule 'supply exactly one of prompt or turn contract.' It does not enumerate every sibling alternative, but the central routing guidance is present.

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