What it does
The workspace credit balance and the entries behind it. Credits are the unit a metered run would be billed in, and the ledger is the only record of one.
Arguments
| Name | Type | Required | Meaning |
|---|---|---|---|
| limit | number | no | How many ledger entries, 1–100 (default 20) |
This table is generated from the literal inputSchema that tools/list returns, so what your client sees and what this page says are the same object:
{
"type": "object",
"properties": {
"limit": {
"type": "number",
"description": "How many ledger entries, 1–100 (default 20)"
}
}
}Request
Paste this, swap the key, and you have called the tool.
curl -s https://topclozer.com/api/mcp \
-H "Authorization: Bearer tcz_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "check_credits",
"arguments": { "limit": 20 }
}
}'Returns
{ balance, entries[], note }. Each entry is id, delta, reason, ref, balance_after, created_at.
The payload arrives inside an MCP content block — one text block whose body is this JSON, pretty-printed. Parse the string; there is no structured-content field.
{
"balance": 0,
"entries": [],
"note": "No product action grants or spends a credit yet, so a zero balance here means the ledger is empty, not that a balance ran out. A TopClozer operator can post an adjustment by hand."
}Worth knowing
The balance is read from the newest entry's balance_after rather than summed, so it reconciles against the statement by eye. No product action writes to this ledger — an operator adjustment is the one path that does — and the `note` field says so rather than leaving a zero to be misread as an exhausted account.
Limits
No request limit. This tool reads the workspace database and costs nothing to serve. The limits that bite in this product are the sending controls — per-sender weekly invite caps, the warm-up ramp, the working-hours window and a randomised gap between actions — and no tool can raise them.
Related tools
get_platform_usage
What this workspace owns and has run: installs, purchases, the hosted seat, credits and the execution ledger
list_installations
What this workspace has installed, where, and what it paid for
All 21 tools are listed on the tool index. Connecting a client is on the Claude setup page, and the protocol details are on the server page.