Pocket Runway

Given a bill the user is holding — from a photo, a PDF, an email, or something they typed — check whether it is already configured as a recurring item in the signed-in Pocket Runway user's plan, and if so how it compares. Extract the merchant name, and where visible the amount and due date, and send only those normalized fields: never the document, the image, or unrelated text. Use this for "I got this bill in the mail, am I already accounting for it", "is this $59.55 Republic Services bill different from what I have planned", or "did my bill amount change". The response reports an exact match, a likely match, a possible match, or none; for each match it gives the configured amount, the configured schedule, the next occurrence, whether the observed amount differs materially, and whether the observed due date is consistent with that schedule. Matching is deterministic name matching — it ignores case, punctuation and corporate suffixes, but it does not know that two differently-named brands are the same company. A "possible" result, or `ambiguous: true`, means Pocket Runway is genuinely unsure: ask the user which item they mean instead of asserting an answer. This tool only reads. It never adds or changes anything.

check_bill_against_plan

Return the signed-in Pocket Runway user's daily safe-to-spend allowance for the current pay period — what is left to spend divided across the days remaining until payday — plus how much of today's allowance is already gone. Use this for "what can I spend today", "how much do I have left for today", or "am I on pace this pay period". Prefer get_runway when the question is about the whole period rather than a single day.

get_daily_allowance

Calculate how much money the signed-in Pocket Runway user can safely spend between now and their next paycheck, after Pocket Runway subtracts every bill, transfer, savings contribution, sinking-fund reserve and other planned obligation still due in the current pay period. Use this for questions like "how much can I spend before payday", "what's actually safe to spend", or "how much of my balance is really available". This is a paycheck-cycle answer computed from the user's own Pocket Runway plan — not a bank balance, and not a generic analysis of transaction history. Note that pay-period funding and the current bank balance are two different things: the obligations are deducted from totalPayPeriodFunding, never from currentBalance.

get_runway

List the bills, recurring transfers and savings/sinking-fund contributions the signed-in Pocket Runway user has coming up, with the amount and expected date of each. By default this covers only what is left in the CURRENT pay period — today through the next paycheck — which is the same set of obligations Pocket Runway subtracts to produce the safe-to-spend figure from get_runway. Use it that way for "what bills are still due before payday", "what's coming out of my account this week", or "what am I still on the hook for". Pass daysAhead to look further out and cross pay-period boundaries: "what's due in the next 30 days", "what bills hit before September 15", "what am I paying next month". When daysAhead is used, each obligation also reports which pay period it lands in, and the totals cover the whole requested window rather than this pay period alone. This tool lists OCCURRENCES on a calendar; to ask whether something is configured to recur at all, use get_recurring_obligations instead.

get_upcoming_obligations

Return what the signed-in Pocket Runway user has CONFIGURED to repeat — recurring bills and subscriptions, standing transfers, and per-paycheck savings contributions — together with the amount, the schedule, and the next date each one is due. Unlike get_upcoming_obligations, this is NOT limited to the current pay period: an item whose next occurrence falls weeks or months from now is still listed, because it is still part of the plan. Use this to answer "is <merchant> already in my plan", "do I already have <merchant> entered", "show me all my recurring bills", "what subscriptions am I paying for", or "when does <bill> hit next". Pass `query` to search by name and `type` to narrow by kind; omit both to list everything. If the user is holding an actual bill and wants it compared against the plan — amount, due date, or whether it is a duplicate — prefer check_bill_against_plan, which does that comparison. One-off, non-repeating entries are deliberately not listed here: a single dated entry is not a recurring arrangement.

get_recurring_obligations

Answer "can I afford this?" by showing what a hypothetical purchase would do to the signed-in Pocket Runway user's safe-to-spend figure and daily allowance for the current pay period. Use this for "can I afford $250 this weekend", "what happens to my runway if I spend $400 today", or any question about a purchase that has not been made. This is a projection only: it never records a transaction, changes a budget, or modifies the user's account in any way. The purchase date must fall inside the current pay period.

simulate_purchase

Explain how the signed-in Pocket Runway user's current pay period is allocated: the income funding it (paycheck, one-time income, money carried over from last period), how much is committed to bills, transfers, savings and sinking funds, how much has been spent so far, and what is left. Use this for "where is this paycheck going", "break down my pay period", or "why is my allowance lower than I expected". Use get_upcoming_obligations instead when the user wants the individual line items rather than the totals.

get_pay_period_summary