```mermaid
flowchart LR
  A["Agent: tools/call get_balance<br/>remit.paymentrequired.com/mcp"] --> V["validate()<br/>tools.js"]
  V --> D["callTool get_balance<br/>mcp.js"]
  D --> E["engine.balance()"]
  E --> CP(("ClickPesa"))
```

# `get_balance` (Remit)

[← Index](../index.md) · [Overview](../overview.md) · [Signer](../signer.md) · [Issued links](../links.md)

> Evidence labels: **CODE** = read in the cited file at the recorded revision/hash; **FIXTURE** = parent-accepted combined cloud fixture run 99/99 (`directory-wave/parent-directory-wave-acceptance.json`), not live; **LIVE-RO** = observed read-only on the live host 2026-10-14 (raw files in `evidence/live-probes/`); **UNVERIFIED** = not executed here. Topology = accepted directory-wave source, **not deployed**. Nothing in this handbook moved money, signed, or activated a card.

## What it does

ClickPesa float (`availableTZS`) and product limits (bank 21,000,000 TZS; mobile/merchant 3,000,000 TZS per transfer). Float is not a transfer maximum.

**Catalog:** remit.paymentrequired.com/mcp (own MCP, independent). **Schema & dispatch:** Definition [`remit:src/tools.js:123`](https://github.com/nuri-com/nuri-clickpesa-remit-mcp/blob/212886c7eedfa314f7de790622ea95632630057b/src/tools.js#L123); dispatch [`remit:src/mcp.js:356`](https://github.com/nuri-com/nuri-clickpesa-remit-mcp/blob/212886c7eedfa314f7de790622ea95632630057b/src/mcp.js#L356)

## Actions / operations

| action | what happens | effect | source |
|---|---|---|---|
| `get_balance` | Available payout liquidity | read | [`remit:src/mcp.js:356`](https://github.com/nuri-com/nuri-clickpesa-remit-mcp/blob/212886c7eedfa314f7de790622ea95632630057b/src/mcp.js#L356) |

## Prerequisites

No account, registration or API key (instructions text). 

## How to use it (exact `tools/call` JSON)

Endpoint: `POST https://remit.paymentrequired.com/mcp` (JSON-RPC 2.0). Placeholders in `<…>` are never real values; secrets (`session`, `wallet_key`) are never pasted into docs or logs.

**get_balance**

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

Expected result (`structuredContent`, shape from code; values illustrative):

```json
{"ok":true,"availableTZS":…,"currency":"TZS","limits":{"minTZS":100,"maxTZSByDestination":{…}},"liquidityNote":"…","minSwapTZS":100,"at":"…"}
```

Plain-JSON form (same handler): `POST /mcp` with `{"tool":"get_balance", …arguments}`; a payment request then comes back as HTTP 402 ([`remit:src/mcp.js:799`](https://github.com/nuri-com/nuri-clickpesa-remit-mcp/blob/212886c7eedfa314f7de790622ea95632630057b/src/mcp.js#L799)).

## Approval, signature and money

No approval or signature; no money moves.

## Failure, peer-down and retry

Stateless read; repeat freely. Provider errors are returned as JSON-RPC error -32602 with `data.code`.

## What was actually observed

LIVE-RO 2026-10-14T18:10Z @212886c: returned JSON-RPC error `balance_unavailable` (ClickPesa generate-token HTTP 403; evidence/live-probes/remit-readonly-calls.json) — the tool is reachable, the upstream provider refused/rate-limited at capture time. Success shape: UNVERIFIED live.