> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allocait.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Action and feedback tools

> Read the action log and send feedback.

Three tools read, comment on and delete entries in the action log. A fourth, `send_feedback`, files a report with Allocait.

## Actions

**list\_actions** `read`

A portfolio's action log: recorded trades and cash movements, newest first, with comments. Cash movements carry the symbol `$CASH`. It returns 20 actions unless you set `limit` (up to 500), and a row has shares, price per share and trade value but no allocation percent. Key arguments: `portfolio_id`, optional `symbol`, `since`, `until` (UTC dates), `limit`. `has_more` says whether more actions match; narrow with `since` or `until` to reach them.

**save\_action\_comment** `write, destructive`

Sets or clears the comment on an action: why the decision was made. A new comment replaces the old one, and `list_actions` shows it, to keep or extend. The trade or cash amount itself never changes. Key arguments: `action_id`, `comment` (`null` clears it).

**delete\_actions** `write, destructive`

Deletes entries from the action log; this can't be undone. Holdings and cash don't change, so it doesn't undo a trade. Ids that aren't yours or are already gone come back in `not_found`. Key arguments: `action_ids` (1 to 100).

## Feedback

**send\_feedback** `write`

Files a report with Allocait. Send it only when the user asks, and leave holdings and account data out. It adds one report and changes nothing in the account. See [Agent feedback](https://docs.allocait.app/guides/agent-feedback.md).

Pick a `topic`:

* `account`: your own account or billing. Needs `details` and a connection with **Read and change** access. On a read-only connection it returns `READ_ONLY_KEY` or `OAUTH_WRITE_NOT_GRANTED` and files nothing.
* `tools`: a bug, an unclear description or a missing tool.
* `early_access`: how a task went. It takes four fields, each up to 1,000 characters: `task` (what you were trying to do), `details` (what happened), `steps` and `expected`. Send at least `task` or `details`.

Read-only connections can send `tools` and `early_access`. The result is `{topic, filed, message}`; an `early_access` report also returns a `ref` for Claude to tell you. The result's message says not to promise a reply or a date. `tool`, `error_code` and `request_id` are kept only when they have the usual shape.

Key arguments: `topic`, `kind` (`tools`: bug, docs, missing\_capability, other; `account`: bug, billing, feature\_request, other; `early_access`: bug, docs, missing\_capability, works\_well, other), `summary` (up to 200 characters), `details` (up to 1,000 characters; required for `account`), optional `task`, `steps`, `expected`, `tool`, `error_code`, `request_id`.

## Next steps

> [card] [Action log](https://docs.allocait.app/concepts/action-log.md)
>
> The record of changes made to your holdings and cash.

> [card] [Agent feedback](https://docs.allocait.app/guides/agent-feedback.md)
>
> How an agent reports a gap in the API, MCP server or docs.

> [card] [Send feedback](https://docs.allocait.app/guides/send-feedback.md)
>
> Which of support, early access and agent feedback to use.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.