MCP tool reference
The worker gives your agent an MCP server with One Horizon tools on every turn. The list below is generated from the same tool catalog the worker registers, so every name, parameter, and availability note matches what your agent receives.
Expand a tool to see its parameters.
Availability
Most tools are registered on every document MCP server the harness starts. A few are conditional:
get_task_details,list_task_comments, andadd_task_commentare present on every real turn, even when the task has no linked documents.get_task_detailstakes no input and always returns the current task, so an agent cannot point it at another task.add_task_commenttakes onlycontentand always posts to the current task.get_parent_detailsis present when the current task has a parent initiative. It takes no input.list_linked_documentsandread_linked_documentare present on every real turn. They cover manually linked documents (a spec, requirement, or similar, not a workflow artifact like plan/research/review/code_summary, which the document-block tools cover). With nothing linked,list_linked_documentsreturns an empty list. A linked document that was deleted or can't be read shows up with anerror(document_not_foundordocument_access_denied) instead of hiding the others.report_workflow_verdictis registered only forreview-mode workflow task turns. It is absent fromplanandcodeturns.report_resultis present on every real turn, in every task mode. Only Execute requires the call.
See documents, tools, and artifacts for how document blocks, review verdicts, and result summaries fit into a turn, and the ACP contract for how session/new delivers this MCP server to your agent.