Getting startedCreate your first initiativeConnect version controlInvite your teamPlan today's work
OverviewQuickstartHarness manifestACP contractDocuments & toolsMCP toolsDistributeRun & monitorBuild cloud agentAgent sessionsReferenceLimits & securityTroubleshooting
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Changelog
  • Docs

Features

  • Roadmap
  • Boards
  • Triage
  • Workflows & agents
  • Progress
  • Insights
  • CLI
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • Support
  • API reference
  • Desktop app
  • SDK
  • Vault
  • QR code generator

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXTikTokYouTubeMedium


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, and add_task_comment are present on every real turn, even when the task has no linked documents. get_task_details takes no input and always returns the current task, so an agent cannot point it at another task. add_task_comment takes only content and always posts to the current task.
  • get_parent_details is present when the current task has a parent initiative. It takes no input.
  • list_linked_documents and read_linked_document are 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_documents returns an empty list. A linked document that was deleted or can't be read shows up with an error (document_not_found or document_access_denied) instead of hiding the others.
  • report_workflow_verdict is registered only for review-mode workflow task turns. It is absent from plan and code turns.
  • report_result is 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.
























PreviousDocuments & toolsNextDistribute

Documents & tools

The MCP tools every harness receives: workflow artifacts, review verdicts, result summaries, and visual artifacts.

Harness manifest

The one.json reference: everything the worker needs to install, verify, and launch your agent.

ACP contract

How the worker drives your agent over the Agent Client Protocol: turn lifecycle, headless behaviors, trust boundaries, and outcome mapping.

Capabilities

Add skills, MCP servers, and plugins, then control which agents and workflow steps can use them.