Kachink

[
  {
    "name": "log-transaction",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Log a one-time income or expense transaction. If the user implies the charge is monthly or recurring (e.g. 'I pay X/mo', 'monthly subscription', 'every month'), use add-recurring instead."
  },
  {
    "name": "edit-transaction",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Edit fields of an existing transaction. Only pass fields that need changing."
  },
  {
    "name": "delete-transaction",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Delete a transaction by its ID."
  },
  {
    "name": "list-transactions",
    "annotations": {
      "readOnlyHint": true
    },
    "description": "Search transactions to find IDs for editing or deleting. Call this before edit-transaction or delete-transaction. Read the ids from structuredContent.transactions, not from the text summary."
  },
  {
    "name": "add-recurring",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Add a recurring transaction that auto-logs every month. IMPORTANT: You MUST ask the user which day of the month (1–28) the charge occurs before calling this tool. Never guess, never use today's date, never assume — always ask explicitly if the user has not stated the day."
  },
  {
    "name": "list-recurrings",
    "annotations": {
      "readOnlyHint": true
    },
    "description": "List all recurring transactions for the user, including paused ones. Read the ids from structuredContent.recurrings, not from the text summary."
  },
  {
    "name": "delete-recurring",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Delete a recurring transaction by its ID. Use list-recurrings to find the ID first."
  },
  {
    "name": "toggle-recurring",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Pause or resume a recurring transaction. Paused recurrings stop auto-logging until resumed. Use list-recurrings to find the ID."
  },
  {
    "name": "set-base-currency",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Change your base currency. All existing transactions will be recomputed to the new currency."
  },
  {
    "name": "add-category",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Create a new spending category for the user. The FIRST time this is ever called, it also imports the 12 default categories into the user's editable list so they can rename or delete any of them. NEVER invent a category the user did not explicitly ask for."
  },
  {
    "name": "rename-category",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Rename one of the user's categories. This relabels every existing transaction and recurring rule that used the old name. If the user has never customized their categories, this first imports the 12 defaults."
  },
  {
    "name": "remove-category",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Remove a category from the user's list. This NEVER deletes transactions. If the category has transactions you MUST pass either remap_to (move them to another existing category) or keep_inactive=true (keep historical transactions under the old label but stop offering it for new logging). If the category is in use and neither option is passed, the tool tells you how many transactions use it so you can ask the user how to proceed."
  },
  {
    "name": "list-categories",
    "annotations": {
      "readOnlyHint": true
    },
    "description": "List the user's Kachink spending categories and how many transactions use each. Call this before renaming or removing a category so you can reference exact names, and whenever you are unsure whether a category the user named actually exists."
  },
  {
    "name": "batch-edit-transactions",
    "annotations": {
      "readOnlyHint": false
    },
    "description": "Recategorize or relabel many Kachink transactions in one call, for example moving every transaction out of one category into another. Provide a filter (which transactions to match) and the fields to set. At least one filter field MUST be provided so you never edit every transaction by accident. Common use: move all transactions from one category to another (filter by category, set category)."
  },
  {
    "name": "show-dashboard",
    "title": "Kachink Dashboard",
    "annotations": {
      "readOnlyHint": true
    },
    "description": "Display the user's finance dashboard for a given month. Pass `month` (YYYY-MM) if the user mentions one; otherwise omit it and the current month is shown."
  },
  {
    "name": "get-month-data",
    "title": "Get month data",
    "annotations": {
      "readOnlyHint": true
    },
    "description": "Fetch finance data for a specific month (internal)"
  },
  {
    "name": "export-my-data",
    "annotations": {
      "readOnlyHint": true
    },
    "description": "Export the user's own data as JSON (transactions, recurring transactions, custom categories, preferences). Use this when the user asks for a copy of their data. Excludes internal identifiers, timestamps, third-party identifiers, and system logs."
  },
  {
    "name": "get-plan",
    "annotations": {
      "readOnlyHint": true
    },
    "description": "Show the user's KACHINK subscription and usage: whether they are on the Kachink Free or Kachink Pro plan, how much of this month's Kachink transaction allowance they have used, how many active recurring rules they have, and their renewal or cancellation date. This is about the user's Kachink account only. It has nothing to do with their ChatGPT subscription."
  }
]