API Guide
Every parameter for every tool. Authoritative source.
The canonical reference lives in the repository so that the running server can serve it via /skill and LLM agents can read it directly:
It’s kept in the repo (and shipped inside the Docker image at /ORKESTRA_SKILL.md) so that there’s exactly one source of truth. This page intentionally doesn’t duplicate the content — duplication is how docs go stale.
What’s in the reference
Section titled “What’s in the reference”- Required vs optional parameters for every tool
- Default values
- Return shape for each tool (single ticket, array, board, error)
- Validation rules (e.g.
exec_orderuniqueness within a parent) - Concrete TOON output examples
See also
Section titled “See also”- Examples — end-to-end workflow walkthroughs
- Troubleshooting — error code recovery
- TOON Format — how to read tool responses