reference · oto actions --help at v0.6.1

oto actions

list and check the actions the project declares (Oto never invokes one)

oto actions [-h] [--project PROJECT] [--on ENTITY] [--by BY] [--at YYYY-MM-DD]
                   [--response FILE] [--note NOTE] [--ready] [--due] [--json]
                   [{list,check,show,record,runs}] [which ...]

Verbs

list prints every action with its readiness on the authored graph
check validates the files against the vocabulary
show <id> [--on <entity>] prints one as the MCP tool definition the caller invokes, inputs bound to the entity
record <id> --on <entity> --by <you> --response <file|-> writes the run the caller performed as a source document and, for a proposal result, the proposal
runs lists the records

which for show and record: the action id

Options

Option	What it does
`--project PROJECT`	project root (default: current directory)
`--on ENTITY`	for show and record: the subject entity's id
`--by BY`	for record: who performed the invocation (required)
`--at YYYY-MM-DD`	for record: the date of the invocation (default today)
`--response FILE`	for record: the response the invocation returned, a file or - for stdin
`--note NOTE`	for record: a note kept with the run
`--ready`	for list: only the actions ready on at least one entity
`--due`	for list: only the scheduled read-only actions whose run is due and that are ready
`--json`	the tool definitions as JSON

Where to use it

What can be done here, on which entities?

oto actions list --project claims --ready

every action the project declares, with its readiness on the authored graph

An agent is about to invoke one.

oto actions show submit-report --project reports --on report.exposure-q2

the MCP tool definition with inputs bound to the entity; Oto never invokes it

The caller invoked it and has the response.

oto actions record submit-report --project reports --on report.exposure-q2 --by "<who>" --response response.json

a run record, a source document and a proposal for the gates

As the terminal prints it

usage: oto actions [-h] [--project PROJECT] [--on ENTITY] [--by BY] [--at YYYY-MM-DD]
                   [--response FILE] [--note NOTE] [--ready] [--due] [--json]
                   [{list,check,show,record,runs}] [which ...]

positional arguments:
  {list,check,show,record,runs}
                        list prints every action with its readiness on the authored graph; check
                        validates the files against the vocabulary; show <id> [--on <entity>]
                        prints one as the MCP tool definition the caller invokes, inputs bound to
                        the entity; record <id> --on <entity> --by <you> --response <file|->
                        writes the run the caller performed as a source document and, for a
                        proposal result, the proposal; runs lists the records
  which                 for show and record: the action id

options:
  -h, --help            show this help message and exit
  --project PROJECT     project root (default: current directory)
  --on ENTITY           for show and record: the subject entity's id
  --by BY               for record: who performed the invocation (required)
  --at YYYY-MM-DD       for record: the date of the invocation (default today)
  --response FILE       for record: the response the invocation returned, a file or - for stdin
  --note NOTE           for record: a note kept with the run
  --ready               for list: only the actions ready on at least one entity
  --due                 for list: only the scheduled read-only actions whose run is due and that
                        are ready
  --json                the tool definitions as JSON