When to use
Useexpenses_read for document_status, get, list. Use expenses for the companion actions. The live tool list determines availability.
Input
Actions
The tool’s schema combines the fields of every action. Each action accepts only its own fields below; sendaction with them.
Read actions
These actions only read. They change nothing.document_status
document_status
What documents queued with from_document became: one job by job_id, or the company’s latest twenty. Each says queued, done (with the expense or income recorded, its review codes and deductibility) or failed (with a code; direction_unknown means ask and queue it again with direction; country_unknown means ask the supplier/customer country and retry with counterparty_country and the direction from the error).
get
get
Read one expense belonging to this company, including its saved version, deductibility and review codes.
list
list
List bounded expense summaries with saved versions, category, classification and settlement balances. Get an expense for its full evidence, review codes and deductibility estimate. Follow next_cursor while has_more and keep filters unchanged.
Output
list and get return expenses with their amounts, category, review and saved version. document_status returns what a queued document became.
The result uses MCP content blocks; JSON payloads are encoded in text and may also appear in structuredContent. Check isError before reading a success payload. When the server declares an outputSchema, it is reproduced below. Check the action result and its declared fields before reporting success.
Declared output schema
Example
Use the actions of this tool in the order shown; its companion tool covers the other actions. These are thearguments of each call, in order.
1
See what the document became