Skip to main content
Glama
Codex Team Workbench

Codex Team Workbench

by 912925635

team_set_history_sync

Enable or disable automatic bounded visible-text sync for a specific board root after user confirmation, retaining existing history without changing native agent or Hook configuration.

Instructions

After explicit user confirmation, enable/disable automatic bounded visible-text sync for this exact board root. An empty expectedRootSessionId is allowed only to cancel an unbound board pending initialization. Existing history is retained; no native agent or Hook configuration is changed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "boardId": "<boardId>",
      "expectedRevision": "<expectedRevision>",
      "expectedRootSessionId": "<expectedRootSessionId>",
      "enabled": "<enabled>",
      "confirmed": "<confirmed>"
    },
    "name": "team_set_history_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYes
enabledYes
confirmedYes
expectedRevisionYes
expectedRootSessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.6

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-destructive, closed-world mutation; the description adds genuinely new behavioral facts: user confirmation is mandatory, existing history is retained, and no native agent or Hook configuration is altered. The special-case rule for an empty expectedRootSessionId is also behavior an agent could not infer from the schema. It does not describe what happens on a revision mismatch, which keeps it below a 5.

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 sentences, front-loaded with the action and its precondition, with no filler. Density is high but each clause carries distinct information; the only cost is that 'bounded visible-text sync' is unexplained jargon.

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

Completeness3/5

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

For a five-required-parameter mutation with no output schema, the description covers the confirmation gate, the retention guarantee, and one edge case, which is meaningful. It still leaves the concurrency contract around expectedRevision and the failure behavior on a stale revision undocumented, which an agent needs before calling this correctly.

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% across five required parameters, so the description must carry the load and only partly does. It clarifies expectedRootSessionId's empty-value semantics and links confirmed to the user-confirmation requirement, but expectedRevision (apparently an optimistic-concurrency token) and boardId's 'exact board root' scoping are never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb pair (enable/disable) and a specific resource (automatic bounded visible-text sync for this exact board root), which is far more than a restatement of the name. It also implicitly separates itself from team_sync_native_history by stating that no native agent or Hook configuration is changed, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one real precondition — 'after explicit user confirmation' — and one narrow permitted case for an empty expectedRootSessionId. It does not say when an agent should choose this over team_sync_native_history or team_bind_session, so the routing decision is left to inference.

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