MCP tool reference
The list below is generated from @repo/worker-runtime's MCP tool catalog, the same data document-server.ts passes to registerTool when it starts the MCP server for a turn. Every name, parameter, and availability note here matches what your agent actually receives — there is no separate hand-written tool description to fall out of sync.
Expand a tool to see its parameters. Required parameters must be present in the call; optional parameters can be omitted.
Availability
Most tools are registered on every document MCP server the runtime starts. A few are conditional:
get_task_detailsandlist_task_commentsrequire the server to start with a client, currenttaskId, andworkspaceId. The orchestrator always supplies these for a workflow-linked task turn, so both tools are present on every real turn, even when the task has no linked documents.get_task_detailstakes no input — it always resolves to the current task, so an agent cannot point it at another task by supplying a different ID.get_parent_detailsrequires the same client/taskId/workspaceId context plus a parent task linked to the current task via apart_ofrelation. It also takes no input and is absent from tasks with no parent.list_linked_documentsandread_linked_documentare registered only when the task has at least one manually-linked document (a spec, requirement, or similar — not a workflow artifact like plan/research/review/code_summary, which the document-block tools below already cover). Absent on tasks with no linked documents.report_workflow_verdictis registered only forreview-mode workflow task turns. It is absent fromplanandcodeturns.report_resultis registered whenever the host supplies a result handler. The orchestrator supplies one for every task mode, so it is present on every real turn.- Prompt every successful mode to call
report_resultonce with a one- or two-sentence, non-technical owner summary. Only Execute requires the call; other current and future modes use the normal final message when it is omitted or fails. Review still reports its structured verdict separately.
See documents, tools, and artifacts for how the document-block tools, review verdicts, and result summaries fit into a turn, and the ACP contract for how session/new delivers this MCP server to your agent.