ExpenseBot

correct_expenses

Destructive

Safely correct the category, business purpose, or explicit attendees on an exact bounded set of recorded expenses. Examples: 'categorize these as Travel', 'add Client kickoff dinner as the business purpose for these meals', or 'add Fred, Rob, and Lamar to last night's business meal'. First use search_expenses to identify the exact rows, then pass their full expenseId values. A grounded preview is automatic: first call with confirm omitted/false, show the exact count and proposed before-to-after changes, and ask once for approval. Only after explicit approval repeat the same operationId, selection, and change with confirm:true. A premature confirm:true is converted to preview. Attendee names must come explicitly from the user; never infer them. attendeeMode add preserves existing attendees, while replace substitutes only the attendee segment. Business purpose and attendees preserve the structured Notes field, including card, description, inbox, and other typed segments. Formula Notes and changes that exceed the Notes limit are skipped safely. The confirmed result reports applied/conflicted/failed counts and supports Undo. This tool does not omit duplicates, change amounts or dates, infer business context, or run broad Calendar matching. For unsupported or more than 100-row cleanup, send the user to https://www.expensebot.ai/review-expenses?source=mcp.

Input Schema

TableJSON Schema

Name	Required	Description
`undo`	No	Undo a completed correction within its Undo window.
`change`	No	Exactly one correction. The selected type determines which matching value field is required.
`status`	No	Read operation status using operationId.
`confirm`	No	Omit/false for preview; true only after explicit approval.
`selection`	No	Exact expenses returned by search_expenses and approved for this bounded correction.
`operationId`	Yes	Stable idempotency key generated once for preview and reused unchanged.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`undo`	No
`change`	No
`status`	Yes
`message`	No
`preview`	No
`success`	Yes
`manifest`	No
`finalAnswer`	No
`operationId`	No
`confirmation`	No
`responseGuidance`	No
`reviewExpensesUrl`	No
`requiresConfirmation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 9, 2026

addedInput schema / properties / change / oneOf

Added value: +[
+  {
+    "properties": {
+      "type": {
+        "const": "category"
+      }
+    },
+    "required": [
+      "category"
+    ]
+  },
+  {
+    "properties": {
+      "type": {
+        "const": "businessPurpose"
+      }
+    },
+    "required": [
+      "businessPurpose"
+    ]
+  },
+  {
+    "properties": {
+      "type": {
+        "const": "attendees"
+      }
+    },
+    "required": [
+      "attendees"
+    ]
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "change": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "confirmation": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "finalAnswer": {
+      "type": "string"
+    },
+    "manifest": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "operationId": {
+      "type": "string"
+    },
+    "preview": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "requiresConfirmation": {
+      "type": "boolean"
+    },
+    "responseGuidance": {
+      "type": "string"
+    },
+    "reviewExpensesUrl": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "undo": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "success",
+    "status"
+  ],
+  "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

Changed8 schema fields changedAug 22, 2026

addedInput schema / properties / change / properties / attendees / description

Added value: +"Attendee names explicitly supplied by the user when type is attendees; never infer names."

addedInput schema / properties / change / properties / businessPurpose / description

Added value: +"User-supplied business purpose to apply when type is businessPurpose."

addedInput schema / properties / change / properties / category / description

Added value: +"Configured expense category to apply when type is category."

addedInput schema / properties / change / properties / type / description

Added value: +"The one correction kind to apply to every exact selected expense."

addedInput schema / properties / selection / description

Added value: +"Exact expenses returned by search_expenses and approved for this bounded correction."

addedInput schema / properties / selection / properties / items / description

Added value: +"One exact receipt identity per selected expense; never broaden this list after preview."

addedInput schema / properties / selection / properties / items / items / properties / expected / properties / category / description
```
Added value: +"Current category observed before preview for conflict detection."
```
addedInput schema / properties / selection / properties / items / items / properties / expected / properties / notes / description
```
Added value: +"Current structured Notes value observed before preview for conflict detection."
```

First observedAug 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description adds far more: an automatic grounded preview with count and before-to-after diffs, premature confirm being downgraded to preview, idempotency via a stable operationId, Notes preservation and Formula Notes/limit skips, applied/conflicted/failed reporting, and Undo support. This is exactly the safety and side-effect detail that matters for a destructive mutation.

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?

Front-loaded with purpose then workflow then constraints, and the examples are useful. It is long and dense for a single paragraph, with a few clauses (e.g., the Notes-limit/Formula skip detail) that could be tightened, but almost every sentence carries operational information.

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 destructive, nested-object mutation with an available output schema, the description covers selection provenance, concurrency expectations via 'expected' fields, preview/confirm gating, idempotency, and failure counts, so an agent has everything needed to call it correctly. Return-value detail is appropriately left to the output schema.

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 description coverage is 100%, so the baseline is 3, but the description still adds meaning: 'repeat the same operationId, selection, and change with confirm:true' explains the sequencing contract, and 'attendeeMode add preserves existing attendees, while replace substitutes only the attendee segment' clarifies replace semantics beyond the schema's terse 'Use add unless...'.

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 bounded precisely ('Safely correct the category, business purpose, or explicit attendees on an exact bounded set of recorded expenses') and enumerates concrete examples. It also carves out what it does NOT do ('does not omit duplicates, change amounts or dates, infer business context, or run broad Calendar matching'), which separates it from the broader update_expense sibling even without naming it.

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?

Prescribes an explicit workflow: first call search_expenses to identify exact rows, then pass full expenseId values, preview automatically, and only confirm after explicit approval reusing the same operationId/selection/change. It also names the exclusion route ('unsupported or more than 100-row cleanup' → review URL), so when-to-use and when-not-to-use are both covered.

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.