ExpenseBot

add_cash_expense

Add an expense without a receipt, or record money a client provided in advance for expenses. Writes directly to the user's expense spreadsheet after confirmation. For an ordinary expense, call list_categories first and provide a configured Expense Account. For a client advance, set isClientAdvance=true and clientName; ExpenseBot reuses or creates the canonical client group, applies Cash advance received, and stores the amount as a negative expense. Use this only for money supplied by a client before related spending, never for vendor refunds, reimbursements, earned fees, retainers, or generic deposits. Use the Manual expense link from get_spreadsheet_url instead when the user needs a reviewed form for multiple entries, credits/refunds, tax or tip breakdowns, per diem, or incomplete details.

Input Schema

TableJSON Schema

Name	Required	Description
`tax`	No	Tax amount
`tip`	No	Tip amount
`city`	No	City/location
`date`	Yes	Expense date (YYYY-MM-DD)
`notes`	No	Notes or description
`total`	Yes	Positive amount paid or received. ExpenseBot stores a client advance as negative.
`category`	No	A configured Expense Account returned by list_categories. Do not invent a category.
`currency`	No	Currency code (default: USD)
`merchant`	No	Merchant/vendor name for an ordinary expense. Not needed for a client advance; ExpenseBot derives it from clientName.
`subtotal`	No	Subtotal before tax
`clientName`	No	Client name for a client advance, in ordinary language. ExpenseBot resolves the canonical Client – Name group.
`isClientAdvance`	No	True only when a client supplied money in advance for expenses. Requires clientName and does not require category.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`expense`	No
`message`	Yes
`success`	Yes
`recordId`	No
`rowNumber`	No
`finalAnswer`	No
`spreadsheetUrl`	No
`responseGuidance`	No
`reviewExpensesUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "expense": {
+      "additionalProperties": true,
+      "properties": {
+        "category": {
+          "type": "string"
+        },
+        "currency": {
+          "type": "string"
+        },
+        "date": {
+          "format": "date",
+          "type": "string"
+        },
+        "isClientAdvance": {
+          "type": "boolean"
+        },
+        "merchant": {
+          "type": "string"
+        },
+        "receivedAmount": {
+          "type": "number"
+        },
+        "recordId": {
+          "type": "string"
+        },
+        "rowNumber": {
+          "minimum": 1,
+          "type": "integer"
+        },
+        "tag": {
+          "type": "string"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "finalAnswer": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "recordId": {
+      "type": "string"
+    },
+    "responseGuidance": {
+      "type": "string"
+    },
+    "reviewExpensesUrl": {
+      "type": "string"
+    },
+    "rowNumber": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "spreadsheetUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "success": {
+      "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.4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses that it writes directly to the spreadsheet after confirmation, reuses or creates the canonical client group, applies 'Cash advance received', and stores advance amounts as negative. These are non-obvious side effects an agent could not infer from the schema. It stops short of stating duplication/permission behavior, so not a full 5.

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

Conciseness4/5

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

Purpose and both modes are front-loaded, and every sentence carries routing or behavioral information. The final exclusion sentence is long and list-heavy, but it earns its place by preventing common misrouting.

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?

For a 12-parameter write tool with an output schema (so return values need not be explained), the description covers both operating modes, prerequisites, side effects, and the alternative path. An agent has everything needed to call it correctly or route elsewhere.

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

Parameters3/5

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

Schema description coverage is 100%, so all twelve parameters are already documented in the input schema, including the negative-storage convention for total and the clientName/isClientAdvance relationship. The description mostly restates those semantics, adding only the list_categories prerequisite. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The description names a specific verb and two distinct modes of the resource: 'Add an expense without a receipt' and 'record money a client provided in advance.' It clearly differentiates from siblings like submit_receipt, parse_expense, add_income, and update_expense by scoping itself to receiptless cash entries and client advances.

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?

It gives explicit preconditions per mode ('call list_categories first and provide a configured Expense Account'; 'set isClientAdvance=true and clientName'), states a strong negative boundary ('never for vendor refunds, reimbursements, earned fees, retainers, or generic deposits'), and names a concrete alternative ('Use the Manual expense link from get_spreadsheet_url instead when...'). This is textbook when/when-not/alternative guidance.

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.