Skip to main content
Glama
Codex Team Workbench

Codex Team Workbench

by 912925635

team_sync_native_history

Reads and saves one bounded page of visible thread messages using validated board/member bindings and cursors, without resuming threads or sending main-chat messages.

Instructions

Read and save one bounded visible-message page directly via public app-server thread/turns/list. Exact bound root, member UUID and fresh parent metadata required; never resumes a thread or sends a main-chat message. Older-page cursors must refer to an existing direct page of this same binding. No private host files, reasoning or tool bodies.

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>",
      "memberId": "<memberId>",
      "expectedNativeId": "<expectedNativeId>"
    },
    "name": "team_sync_native_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYes
memberIdYes
beforeRecordIdNo
expectedNativeIdYes

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 declare readOnlyHint=false and destructiveHint=false, and the description is consistent with that by framing the tool as 'Read and save'. It adds genuine behavioral detail beyond the annotations: it names the underlying public API surface, states that no private host files, reasoning, or tool bodies are captured, and constrains cursor validity to an existing direct page of the same binding.

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 tight sentences, front-loaded with the operation and followed by preconditions and exclusions; nothing is redundant. The wording is telegraphic and jargon-dense ('bounded visible-message page', 'same binding'), which costs a little readability for the compression gained.

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?

There is no output schema and the annotations cover only the safety profile, so the description has to explain the mutation and its limits — which it does for scope and side effects. What it leaves incomplete is the parameter contract: for a tool requiring three inputs at 0% schema coverage, the meaning and format of expectedNativeId and beforeRecordId remain underspecified.

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% for four string parameters, so the description must carry the meaning. It gestures at each concept — 'bound root' (boardId), 'member UUID' (memberId), 'fresh parent metadata' (expectedNativeId), and 'older-page cursors' (beforeRecordId) — but never maps a concept to a parameter name or explains the expected format of the opaque native/parent identifier, so the agent must guess the correspondence.

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 and resource — 'Read and save one bounded visible-message page directly via public app-server thread/turns/list' — which is precise enough to separate this from generic record reads/writes. It stops short of naming any sibling (e.g. team_import_thread_page or team_set_history_sync), so the distinction is inferred from the operation described rather than stated.

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 real preconditions ('Exact bound root, member UUID and fresh parent metadata required') and negative boundaries ('never resumes a thread or sends a main-chat message'), which help an agent decide it is applicable. However, it never routes to an alternative or says explicitly when another page/import tool should be chosen instead, leaving the selection logic to inference.

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