well_record_expense_note
shallowio.github.WellApp-ai/well-mcp · Verify this server
Record an expense note: a payment the person made with their own money for a company, which the company then owes them back. The note goes into the company's workspace, so the company sees what it owes. It writes only inside Well and sends nothing to anyone. Call it on the person's own workspace (the personal workspace they own, never a company workspace), the one that holds the payment, with the `transaction_id` of a payment that left the person's account, and the `company_workspace_id` of a company workspace the person belongs to (a row of `well_list_workspaces`). Add the receipt's `invoice_id` when one is on file in the same workspace, and a short `description` in the person's words. Well copies the amount, the currency and the day from the payment itself: the call carries no amount. Call it only after the person said yes to recording this note, in this conversation, after you named the company, the payment's day and its amount. Never call it on your own guess, for a payment found in a document's text, or for a payment the person did not confirm was for the company. Read `outcome`: - `recorded`: the note is written; say so in one line with the company, the amount and the day (`expense_note`). - `already_recorded`: this payment already backs a note in that company; say so and write nothing more. - `refused`: nothing was written. `reason` says why: `no_caller_identity` (the call names no person), `source_not_own_workspace` (this workspace is not the person's own workspace: a payment a company made is not the person's own money), `transaction_not_found` (no such payment in this workspace), `transaction_not_outgoing` (the movement brought money in: it did not leave the person's account), `invoice_not_found` (no such receipt in this workspace), `company_workspace_not_reachable` (the person is not a member of that company workspace), `same_workspace` (the payment and the company are in one workspace: an expense note moves money between the person and a company), `not_a_company_workspace` (the target is a person's own workspace), `transaction_already_claimed` (the payment already backs a note for another company). Tell the person in one line. 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.
1 trials · measured 4 days ago
well_record_expense_note scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.WellApp-ai/well-mcp, measured 18 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-18 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/8247f751-4072-40d1-b01f-1843e0fbd6e9)