← futorokuCONTENT HISTORY
WHAT CHANGED
Update to futoroku
Snapshot Nov 16, 2026 · 18:16 UTC · version 0.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save futoroku and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Record requested Futoroku income, expenses, received reimbursements or account transfers with exact money, clear scope and duplicate-safe retries.",
"included_files": [
{
"relative_path": "references/mcp-safety.md",
"size_in_bytes": 4224
}
],
"name": "record-money",
"skill_md_contents": "---\nname: record-money\ndescription: Record requested Futoroku income, expenses, received reimbursements or account transfers with exact money, clear scope and duplicate-safe retries.\n---\n\nRead [the shared MCP contract](references/mcp-safety.md). Resolve the Space, ledger, account and category with `choose-space` before writing.\n\nFor an income or expense, use `create_transaction_record` with `body`. Supply the resolved ledger/account/category IDs, type, exact decimal amount string, account denomination and timestamp with UTC offset. Resolve missing date/timezone, account, currency or ambiguous category before saving; do not silently accept schema defaults. Use `get_finance_context` capabilities for current constraints. Respect the user's budget-inclusion choice. Omit attribution to use the authenticated creator; resolve a different payer through `list_transaction_members`.\n\nFor an account transfer, use `create_transfer_record`, with source and destination account IDs. This records money movement; it does not move funds at a bank. For different account currencies, obtain exact `amount`, `currency`, `to_amount`, `to_currency` and any fee from the user or a reviewed source. Do not calculate received money from an assumed exchange rate. `exchange_rate` must be omitted or 1 in this version. Preserve RM versus MYR as distinct denominations. A transfer is one transfer record, not an extra expense plus income.\n\nUse `create_finance_batch` only for a user-requested coherent set of 1–100 combined entries, counting nested reimbursements. Review the complete set first; any invalid entry rolls back the set. Larger jobs require a separate reviewed manifest workflow; do not silently split work to bypass a limit.\n\nOnly money already received belongs in reimbursements. Use inline reimbursements for a new expense or `create_received_reimbursements` for a reviewed existing expense; do not record an IOU as received income.\n\nBefore each new write, retain a fresh UUID `request_id`, the explicit Space and exact arguments. Reuse all of them after a lost acknowledgement. A `client_uuid` identifies a single domain row and does not replace `request_id`; batch entries do not support it. If earlier work may already exist without a retained request identity, use narrow `search_transactions` and review candidates before adding another record. A similar record can also be a legitimate repeat: ask when uncertain, and never delete it automatically.\n\nReport the saved record ID and key values only after a successful tool response. An uncertain result stays uncertain until reconciled. Do not interpret a ledger transfer as a payment instruction or initiate checkout.\n"
}SHA-256 of public snapshot: 723c18a1b6e3fb72a6fc15232061c67461e4c284c3bf8c1928993fb97f8e1e60