ExpenseBot

add_income

Log exactly one user-confirmed income payment manually (cash, check, Stripe payout, etc.). Never loop this tool over a statement, export, table, or multi-row list. For two or more payments, use add_income_from_csv for CSV/TSV/text or add_income_from_file for an image/PDF; those tools stage a duplicate-checked preview and require confirmation before writing. Writes to the Income tab of the user's expense spreadsheet. Useful for income that isn't auto-detected from Gmail or Plaid. Call list_income_categories first and use one of its fixed tax categories; an omitted category defaults to Service income and an unknown category is rejected.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Tag for client/project attribution
`date`	Yes	Income date (YYYY-MM-DD). Required. Use the date the user gives; for "today" send today's calendar date in their timezone. If no date was given, ask.
`fees`	No	Processor/transfer fees deducted
`notes`	No
`amount`	Yes	Income amount (>0)
`source`	Yes	Who paid you (client name, customer, etc.)
`category`	No	A category returned by list_income_categories (optional; defaults to Service income)
`currency`	No	Currency code (default: home currency)
`reference`	No	Invoice or transaction reference
`description`	No	What the income was for
`taxCollected`	No	Sales tax/GST/HST collected
`paymentMethod`	Yes	How you got paid. Canonical rails are Cash, Check, Bank transfer, Wallet app, Credit/Debit card, Payment processor, or Other; common labels such as Stripe and Venmo are normalized.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`deduped`	No
`message`	Yes
`success`	Yes
`recordId`	No
`rowNumber`	No
`matchedRow`	No
`tabCreated`	No
`finalAnswer`	No
`destinations`	No
`responseGuidance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

changedInput schema / properties / date / description

Previous value: -"Income date (YYYY-MM-DD). Defaults to today."New value: +"Income date (YYYY-MM-DD). Required. Use the date the user gives; for \"today\" send today's calendar date in their timezone. If no date was given, ask."

changedInput schema / required

Previous value: -[
-  "amount",
-  "source",
-  "paymentMethod"
-]New value: +[
+  "amount",
+  "source",
+  "paymentMethod",
+  "date"
+]

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "deduped": {
+      "type": "boolean"
+    },
+    "destinations": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "finalAnswer": {
+      "type": "string"
+    },
+    "matchedRow": {
+      "additionalProperties": true,
+      "properties": {
+        "amount": {
+          "type": "number"
+        },
+        "currency": {
+          "type": "string"
+        },
+        "date": {
+          "format": "date",
+          "type": "string"
+        },
+        "rowNumber": {
+          "minimum": 1,
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "recordId": {
+      "type": "string"
+    },
+    "responseGuidance": {
+      "type": "string"
+    },
+    "rowNumber": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "tabCreated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "message"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 25, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "description": "Standard ExpenseBot tool result envelope. `message` is the human-readable summary the AI cites; `data` is the structured payload (totals, breakdowns, ids, etc.). On failure, `success` is false and `error` carries a code/message/hint triple.",
-  "properties": {
-    "data": {
-      "additionalProperties": true,
-      "description": "Structured payload. Shape varies per tool — common keys: total, breakdown, comparison, sampleMeta, ids, expenseId, reportId, signupUrl, results.",
-      "type": "object"
-    },
-    "error": {
-      "additionalProperties": true,
-      "description": "Present only when success === false.",
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "hint": {
-          "type": "string"
-        },
-        "message": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "message": {
-      "description": "Human-readable result text. Always present on success; prefer rendering this verbatim before any further reasoning.",
-      "type": "string"
-    },
-    "sampleMeta": {
-      "additionalProperties": true,
-      "description": "Set when the underlying dataset was truncated. isTruncated=true means the agent saw a sample of `sampleCount` of `totalCount` rows; aggregate totals are still accurate.",
-      "properties": {
-        "isTruncated": {
-          "type": "boolean"
-        },
-        "sampleCount": {
-          "type": "integer"
-        },
-        "totalCount": {
-          "type": "integer"
-        }
-      },
-      "type": "object"
-    },
-    "success": {
-      "description": "False on tool errors; check before reading `data`.",
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}New value: +null

First observedAug 10, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds real behavioral context: the write target (Income tab of the expense spreadsheet), the single-payment constraint, that sibling tools stage a duplicate-checked preview requiring confirmation, and that an unknown category is rejected while an omitted one defaults to Service income.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core constraint (exactly one payment) in the first sentence, then the anti-pattern, then alternatives, then destination and category rule. Every sentence carries a distinct instruction with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation. For a 12-param mutation tool with annotations, the description covers the cardinality rule, the sibling routing, the write destination, and the category prerequisite — everything an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 92%, so the baseline is 3. The description still adds value beyond the schema by mandating the list_income_categories lookup and stating the rejection/default behavior for the category parameter, plus the paymentMethod normalization note is reinforced in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Log exactly one user-confirmed income payment manually') plus concrete scope ('one', 'manually') and enumerates example rails. It explicitly differentiates itself from add_income_from_csv and add_income_from_file, so an agent can pick it apart from siblings without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('income that isn't auto-detected from Gmail or Plaid'), explicit when-NOT ('Never loop this tool over a statement, export, table, or multi-row list'), and names the exact alternatives for the two-or-more case along with the condition that selects them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ExpenseBot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.