Issues · pingdotgg/t3code

Summary

The Orchestrator MCP Server document says the server exposes eleven orchestration tools and does not mention the four registered recurring-task tools. At the same commit, OrchestratorToolkit registers fifteen tools, including schedule_task, list_scheduled_tasks, update_scheduled_task, and delete_scheduled_task. Readers using this document to discover orchestration capabilities cannot find the existing recurring-task workflow.

Steps to reproduce

The documentation inspection below was executed against main at commit 4ee6bfd50ef4a089440d5c3662db2298da9cc50e. It requires a checkout of that revision and Python 3, and does not start T3 Code or execute any scheduling operations.

Open docs/orchestration-v2/orchestrator-mcp-server.md at that revision. Read the Tool Surface section and search the document for each of the four recurring-task tool names.

Compare the document with OrchestratorToolkit in apps/server/src/mcp/toolkits/orchestrator/tools.ts. The following read-only command runs from the repository root.

1	python3 - <<'PY'
2	from pathlib import Path
3	import re
4	text = Path('apps/server/src/mcp/toolkits/orchestrator/tools.ts').read_text()
5	registered = re.search(r'export const OrchestratorToolkit = Toolkit.make\((.*?)\);', text, re.S).group(1)
6	variables = re.findall(r'\b(\w+Tool)\b', registered)
7	names = dict(re.findall(r'(\w+Tool) = Tool.make\("([^"\n]+)"', text))
8	doc = Path('docs/orchestration-v2/orchestrator-mcp-server.md').read_text()
9	print(re.search(r'The server exposes[^\n]+', doc).group(0))
10	print('Registered OrchestratorToolkit tools:', len(variables))
11	print('Registered tools absent from the document:', ', '.join(names[name] for name in variables if names[name] not in doc))
12	PY

Expected behavior

The document's description of the tools exposed by the existing endpoint should agree with its registered toolkit. A reader should be able to discover the existing recurring-task tools from that description or a direct reference to their authoritative documentation. The repository's documentation policy permits rewriting or removing inaccurate guidance, so this does not require maintaining a duplicate catalog of schemas.

Actual behavior

The command exited with status 0 and printed:

text

1	The server exposes eleven orchestration tools.
2	Registered OrchestratorToolkit tools: 15
3	Registered tools absent from the document: schedule_task, list_scheduled_tasks, update_scheduled_task, delete_scheduled_task

The document contains no occurrence of those four names. Their tool definitions, handlers, and HTTP toolkit registration are present at the inspected revision. This report concerns documentation accuracy and discoverability; runtime scheduling behavior was not tested.

Evidence

Expected source: AGENTS.md documentation policy says to rewrite or remove affected text when a documented decision or constraint changes. The Orchestrator MCP Server purpose and endpoint description describes the exposed endpoint, and its Tool Surface section makes the concrete eleven-tool claim.

Failure source: The executed document/source comparison above found fifteen registrations in OrchestratorToolkit and no document occurrence of the four recurring-task tool definitions. Their handlers belong to the toolkit that McpHttpServer registers and includes in its HTTP layer.

Evidence provenance: observed

Local verification: reproduced

Reproduction completeness: complete

The primary observed failure is the document/source mismatch. Registration and handler references support which inventory the document describes. No MCP call, test suite, or provider session was run to establish a runtime defect. The document-set README calls the broader set target architecture; this report is limited to this page's present-tense claim about the exposed toolkit and its missing existing recurring-task capability.

Restoration check

At the revision being reviewed, compare the exposed toolkit with the document again. The description should no longer claim eleven tools for a fifteen-tool toolkit, and should either identify the existing recurring-task capability or direct readers to its authoritative reference. Removing the stale count alone leaves the discoverability failure; adding recurring-task guidance while retaining the stale count leaves the inventory inaccurate. Existing tool registration and scheduling behavior need no change to close this documentation report.

JJulius Marminge19d ago

Note

Grok responding on behalf of Julius.

Triage

Thanks for this, @coygeek. The read-only compare script made it quick to check.

What I found

Confirmed on main at 4ee6bfd. This is a documentation mismatch, not a runtime scheduling failure.

OrchestratorToolkit in apps/server/src/mcp/toolkits/orchestrator/tools.ts registers 15 tools, but docs/orchestration-v2/orchestrator-mcp-server.md still says "The server exposes eleven orchestration tools". The page doesn't mention schedule_task, list_scheduled_tasks, update_scheduled_task, or delete_scheduled_task. Their handlers are in handlers.ts, and the orchestrator MCP integration test already covers create, list, pause, and delete.
The Tool Surface section also doesn't agree with itself. It has twelve headings, and t3_thread_launch is registered on ProjectToolkit, which is mounted on the same /mcp endpoint, not on OrchestratorToolkit.
Provider sessions aren't missing anything. schedule_task is already described on the tool itself and in T3OrchestrationInstructions.

Likely fix area

One option is to drop the hard-coded count and add a short note that this toolkit also covers recurring scheduled tasks, with a pointer to tools.ts. That fits the documentation guidance in AGENTS.md. The alternative is to list all four schemas in full.
The Purpose and Verification lists leave out the same capability, so they could be fixed in the same edit. t3_thread_launch could be labeled as a project-toolkit tool.

A maintainer will decide on the fix direction.

Oonly21mil4d ago

#15699 was deferred on 2026-10-14 under Read this first, with a request to ask here for a documentation-only exception. I'd like to ask for that exception.

docs/orchestration-v2/orchestrator-mcp-server.md still says the server exposes eleven orchestration tools and never mentions schedule_task, list_scheduled_tasks, update_scheduled_task or delete_scheduled_task. I have a local candidate that changes only that file (41 lines, no runtime code). It drops the count, points to OrchestratorToolkit as the full list, notes that t3_thread_launch comes from ProjectToolkit, and adds a short scheduled-tasks section. I won't open a PR unless a maintainer agrees to the exception here.

JJulius Marminge2d ago

Reproduced the documentation comparison on current main at b5a226e49c. The page still says eleven tools; OrchestratorToolkit registers seventeen, and all four recurring-task names remain absent from the page. No duplicate found in the paged open-issue scan. This confirms the documentation mismatch only; runtime scheduling was not tested.

JJulius Marminge2d ago

Confirmed the documentation mismatch on defb7e6e6b: seventeen registered tools, eleven claimed, and all four scheduling names absent. Updated existing fix #23206 (#23199) with the reviewed documentation correction and unsigned-webhook warning. The read-only comparison and scoped format check pass; runtime scheduling was not exercised.

Ccoygeek2d ago

Rechecked at main 96bae546: the page still says eleven tools, while OrchestratorToolkit registers seventeen, and all four recurring-task tool names remain absent. The same mismatch is present in v0.1.1. #23199 proposes the correction but is still open, so I'm keeping this issue open pending the merged documentation fix. This was a read-only documentation/source comparison; runtime scheduling was not tested.

[Bug]: Orchestrator MCP documentation omits recurring-task tools#15670