OMP Tandem

Overview Schema Source Related Servers Discussions Admin

tandem_start

Initiate a task by supplying a prompt or structured contract, with options for mode, execution profile, and timeout, to engage an AI peer in collaboration.

Instructions

Start a task with exactly one of prompt or structured contract. Returns immediately.

Base constraints/owned files stay fixed; each follow-up has a new goal and criteria. project_context_id pins product rules/decisions. Only the coordinator sets question timeout. Think: collaboration; analyze: read/search; work: edits/shell, NOT sandboxed.

Input Schema

TableJSON Schema

Name	Required	Default
`cwd`	Yes
`mode`	No	analyze
`prompt`	No
`contract`	No
`execution`	No
`review_id`	No
`review_stage`	No
`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

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses immediate return, non-sandboxed work mode, and a permission constraint. However, it omits error handling, side effects, or what happens on invalid input (e.g., both prompt and contract given). This is adequate but not thorough.

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?

Three short paragraphs, front-loaded with the core purpose. The mode explanation is efficient and the 'NOT sandboxed' note is critical. No redundancy, though structure could be improved with headers.

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?

With 10 parameters and no annotations, the description is incomplete. It fails to explain the execution sub-object, review parameters, project_context_id beyond a single note, and the overall flow. The output schema covers return values, but parameter semantics are under-specified for a tool of this complexity.

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 0%, so the description must compensate. It adds meaning to the mode parameter and clarifies the exclusivity of prompt/contract. It does not explain cwd, execution, review_id, review_stage, timeout_seconds, or question_timeout_seconds (beyond a note). Partial compensation, but significant gaps remain.

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 'Start a task' and the key constraint 'exactly one of prompt or structured contract'. It clearly distinguishes the tool's entry-point role from siblings like tandem_continue and tandem_review, and mentions immediate return.

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?

Provides context on follow-up behavior ('each follow-up has a new goal and criteria'), explains mode semantics (think/analyze/work), and notes a coordination rule (only the coordinator sets question timeout). It does not explicitly exclude use cases for siblings, but the guidance is clear enough for typical selection.

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