# \[Bug\]: Orchestrator MCP documentation omits recurring-task tools · Issue \#15670 · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/issues/15670)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

State: backlog

Priority: 0

## Description

[Discussion and activity](https://git.cafe/pingdotgg/t3code/issues/15670)

---

## 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.

1. 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.
2. Compare the document with `OrchestratorToolkit` in `apps/server/src/mcp/toolkits/orchestrator/tools.ts`. The following read-only command runs from the repository root.

```sh
python3 - <<'PY'
from pathlib import Path
import re
text = Path('apps/server/src/mcp/toolkits/orchestrator/tools.ts').read_text()
registered = re.search(r'export const OrchestratorToolkit = Toolkit.make\((.*?)\);', text, re.S).group(1)
variables = re.findall(r'\b(\w+Tool)\b', registered)
names = dict(re.findall(r'(\w+Tool) = Tool.make\("([^"\n]+)"', text))
doc = Path('docs/orchestration-v2/orchestrator-mcp-server.md').read_text()
print(re.search(r'The server exposes[^\n]+', doc).group(0))
print('Registered OrchestratorToolkit tools:', len(variables))
print('Registered tools absent from the document:', ', '.join(names[name] for name in variables if names[name] not in doc))
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
The server exposes eleven orchestration tools.
Registered OrchestratorToolkit tools: 15
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](https://github.com/pingdotgg/t3code/blob/4ee6bfd50ef4a089440d5c3662db2298da9cc50e/AGENTS.md#documentation) says to rewrite or remove affected text when a documented decision or constraint changes. The [Orchestrator MCP Server purpose and endpoint description](https://github.com/pingdotgg/t3code/blob/4ee6bfd50ef4a089440d5c3662db2298da9cc50e/docs/orchestration-v2/orchestrator-mcp-server.md#L3-L38) describes the exposed endpoint, and its [Tool Surface section](https://github.com/pingdotgg/t3code/blob/4ee6bfd50ef4a089440d5c3662db2298da9cc50e/docs/orchestration-v2/orchestrator-mcp-server.md#L184-L201) makes the concrete eleven-tool claim.
- Failure source: The executed document/source comparison above found fifteen registrations in [OrchestratorToolkit](https://github.com/pingdotgg/t3code/blob/4ee6bfd50ef4a089440d5c3662db2298da9cc50e/apps/server/src/mcp/toolkits/orchestrator/tools.ts#L240-L256) and no document occurrence of the four [recurring-task tool definitions](https://github.com/pingdotgg/t3code/blob/4ee6bfd50ef4a089440d5c3662db2298da9cc50e/apps/server/src/mcp/toolkits/orchestrator/tools.ts#L97-L146). Their [handlers](https://github.com/pingdotgg/t3code/blob/4ee6bfd50ef4a089440d5c3662db2298da9cc50e/apps/server/src/mcp/toolkits/orchestrator/handlers.ts#L36-L61) belong to the toolkit that [McpHttpServer registers](https://github.com/pingdotgg/t3code/blob/4ee6bfd50ef4a089440d5c3662db2298da9cc50e/apps/server/src/mcp/McpHttpServer.ts#L663-L667) and includes in its [HTTP layer](https://github.com/pingdotgg/t3code/blob/4ee6bfd50ef4a089440d5c3662db2298da9cc50e/apps/server/src/mcp/McpHttpServer.ts#L711-L733).
- 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](https://github.com/pingdotgg/t3code/blob/4ee6bfd50ef4a089440d5c3662db2298da9cc50e/docs/orchestration-v2/README.md#L1-L5) 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.

## Area

Docs

## Impact

Minor bug or occasional failure. The observed impact is incomplete capability discovery when reading the orchestration documentation; no failed runtime workflow is claimed.

## Version or commit

`main` at `4ee6bfd50ef4a089440d5c3662db2298da9cc50e`.

## Before submitting

- [x] I searched existing issues and did not find a duplicate.
- [x] I included enough detail to reproduce or investigate the problem.