well_get_transaction_category_rationale

io.github.WellApp-ai/well-mcp · Verify this server

Explain why one transaction sits in its category: the provenance of the category line, read from the transaction and the classifier's receipt of it. `explanation.kind` says which holds. `user`: a person picked the category, `date` is the pick. `affirmed`: the classifier put it there and a person confirmed it, `date` is the confirmation. `rule`: a fixed rule set it, with no date. `matches_rule`: the classifier put it there under the written rule as it still reads, `line` is that rule line verbatim and `rule_source` says whose text it is. `rule_changed`: the written rule changed after the classifier put it there, quote no line. `no_rule`: the classifier put it there and no written line names the category, `date` is the sorting. `no_record`: no record of the sorting is stored. Quote `line` word for word and never compose a reason. Writes nothing. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.