casino-internal-tools

name	casino_internal_tools
description	Use the casino internal HTTP tool server for member lookup, reports, agent settlement, and monthly CSV exports.
metadata	{"openclaw":{"requires":{"bins":"[Truncated]"}}}

Casino Internal Tools Skill

Use this skill when the user asks about:

• member profile lookup
• member history or transaction history
• game ledger reports
• cashflow / deposit / withdraw reports
• single-agent settlement
• all-agent monthly settlement export with CSV

Base rule

This skill uses an existing HTTP tool server.

Do not invent backend URLs. Do not scrape the casino site directly. Always call the local/internal tool server first.

Assume the tool server base URL is provided by the operator. If it is not given, ask for it before continuing.

Default example:

http://<host>:3000

Required headers

For most requests, send:

Content-Type: application/json
x-actor-id: finance-1
x-role-ids: finance-manager
x-query-reason: user-request

If the exact actor or role context is known, use that instead. If the operator gives a different actor or role mapping, follow that mapping.

Tool selection rules

Member lookup

Use:

• POST /tools/member-lookup

Example body:

{
  "lookupBy": "account",
  "lookupValue": "heartbeat"
}

Single agent monthly settlement

Use:

• POST /tools/agent-settlement-report

Example body:

{
  "parentAccount": "99jj99",
  "month": "2026-03"
}

All active agents monthly settlement with CSV

Use:

• POST /tools/agent-settlement-overview-report

Example body:

{
  "month": "2026-03"
}

Game ledger report

Use:

• POST /tools/game-ledger-report

Cashflow report

Use:

• POST /tools/cashflow-report

Deposit report

Use:

• POST /tools/deposit-report

Withdraw report

Use:

• POST /tools/withdraw-report

Platform credit report

Use:

• POST /tools/platform-credit-report

Response reading rules

On success, expect:

{
  "tool": "...",
  "ok": true,
  "data": {}
}

Read in this order:

1. data.normalizedRows
2. data.metrics
3. data.totals
4. data.csv if export is needed

For agent_settlement_overview_report, prefer:

1. data.normalizedRows
2. data.csvHeaders
3. data.csv
4. data.totals.overall

Error handling

If response is:

{
  "ok": false,
  "error": {
    "code": "SESSION_EXPIRED"
  }
}

Do not guess the answer. Tell the operator the internal tool session must be refreshed.

Useful session endpoints:

• GET /session/status
• POST /session/update

Export behavior

If the user asks for a table:

• use normalizedRows

If the user asks for export or CSV:

• use agent_settlement_overview_report
• return or save data.csv

Operational constraints

• Payment handling fees come from the payment report integration
• Month-end dates are already normalized by the tool server
• Do not recompute totals if totals.overall is already present unless the user explicitly asks for verification
• If the tool server base URL is unknown, stop and ask for it