`get_finance_allocations`

Read-only

Calls GET /api/finance/allocations as the signed-in person · REST reference

The voucher-pool credit for each donation

A BARE ARRAY. One row per donation — this is a VIEW over the ledger, not an :Allocation node; nothing of the kind exists in the graph. Reversed gifts appear here too, since the row set is the same one /donations returns. status is derived, not stored: DISTRIBUTED when the donation's own status is ALLOCATED and PENDING for literally every other status, chargebacks included — so a DISPUTED gift reads as PENDING here.

Arguments

This tool takes no arguments.

Example call

A client sends this over the MCP session; Claude and other agents build it for you. The values are placeholders — the shape is real.

json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_finance_allocations",
    "arguments": {}
  }
}

Result

On success (HTTP 200) the tool returns one text item holding the API's JSON, pretty-printed.

One voucher-pool credit per live donation.

json

[
  {
    "amount": 1,
    "donationId": "11111111-1111-4111-8111-111111111111",
    "id": "11111111-1111-4111-8111-111111111111",
    "status": "DISTRIBUTED",
    "type": "VOUCHER_POOL",
    "createdAt": 1
  }
]

Fields

Field	Type	Description
`[].amount`	integer	Voucher-pool credit in CENTS — the recorded split, or 70% of the gross when none is recorded.
`[].createdAt`	integer	Epoch MILLISECONDS, straight off the DAL.
`[].donationId`	string (uuid)
`[].id`	string (uuid)	The DONATION's id — the same value as donationId. There is no allocation entity to have an id of its own.
`[].status`	"DISTRIBUTED" \| "PENDING"	Derived from the donation's status, as above.
`[].type`	"VOUCHER_POOL"

When it fails

A failed call returns isError: true with the API's message as text.

403: Authenticated, but the caller holds none of the required permissions.

What the model is shown

This is the tool exactly as the server lists it in tools/list. The description starts with the REST call it makes.

json

{
  "name": "get_finance_allocations",
  "description": "GET /api/finance/allocations — A BARE ARRAY. One row per donation — this is a VIEW over the ledger, not an `:Allocation` node; nothing of the kind exists in the graph. Reversed gifts appear here too, since the row set is the same one `/donations` returns. `status` is derived, not stored: `DISTRIBUTED` when the donation's own status is `ALLOCATED` and `PENDING` for literally every other status, chargebacks included — so a DISPUTED gift reads as PENDING here.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false
  }
}