Skip to main content
Glama

update_expense

Destructive

Update a single existing expense row's category, tag, merchant or business purpose (e.g. 'recategorize expense X to Meals', 'tag it Client – Acme'). Identify it only by the exact expenseId from search_expenses (the full Receipt ID from Column Q); never a date, displayed number or sheet row number. Two-phase: calls with confirm omitted/false return a current→proposed preview and change nothing; after user confirmation, confirm:true applies it. If the expense is not found, search once for a current exact expenseId; never retry the same stale ID. If a business-purpose update exceeds the Notes capacity, stop and send the user to https://www.expensebot.ai/review-expenses?source=mcp. fields.paidWith edits only the optional Paid with bookkeeping label (no status/settlement change; blank clears it); reuse expectedPaidWith from the preview on confirm. Amounts, dates and raw notes require Review Expenses. Does not create or delete rows. Same change on several rows or attendees: correct_expenses; leave rows out: omit_expenses.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "expenseId": "<expenseId>",
      "fields": "<fields>"
    },
    "name": "update_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYesPartial update object. Include one or more of these optional keys; omit every field that should remain unchanged.
confirmNoOmit or false = preview only (no write). Must be exactly true to apply the change.
expenseIdYesExact full Receipt ID from Column Q, returned as expenseId by search_expenses.
expectedPaidWithNo

Output Schema

NameRequiredDescriptionDefault
dataYes
messageYes
successYes
finalAnswerNo
responseGuidanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / data / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / data / properties
      Removed value: -{
      -  "applied": {
      -    "type": "boolean"
      -  },
      -  "diff": {
      -    "items": {
      -      "additionalProperties": true,
      -      "properties": {
      -        "column": {
      -          "type": "string"
      -        },
      -        "columnLetter": {
      -          "type": "string"
      -        },
      -        "field": {
      -          "type": "string"
      -        },
      -        "from": {},
      -        "to": {}
      -      },
      -      "required": [
      -        "field",
      -        "from",
      -        "to"
      -      ],
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  "dryRun": {
      -    "type": "boolean"
      -  },
      -  "expectedPaidWith": {
      -    "additionalProperties": false,
      -    "properties": {
      -      "operationId": {
      -        "type": "string"
      -      },
      -      "parentFingerprint": {
      -        "type": "string"
      -      },
      -      "revision": {
      -        "minimum": 0,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "revision",
      -      "parentFingerprint",
      -      "operationId"
      -    ],
      -    "type": "object"
      -  },
      -  "expenseId": {
      -    "type": "string"
      -  },
      -  "preview": {
      -    "type": "boolean"
      -  },
      -  "reviewExpenseUrl": {
      -    "type": "string"
      -  },
      -  "unmapped": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  }
      -}
    • removedOutput schema / properties / data / required
      Removed value: -[
      -  "applied",
      -  "expenseId",
      -  "diff",
      -  "unmapped"
      -]
  2. Changed3 schema fields changed
    • addedInput schema / properties / expectedPaidWith
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "operationId": {
      +      "type": "string"
      +    },
      +    "parentFingerprint": {
      +      "type": "string"
      +    },
      +    "revision": {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "revision",
      +    "parentFingerprint",
      +    "operationId"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / fields / properties / paidWith
      Added value: +{
      +  "description": "Nickname, at most last4. Use alone; empty clears override.",
      +  "maxLength": 60,
      +  "type": "string"
      +}
    • addedOutput schema / properties / data / properties / expectedPaidWith
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "operationId": {
      +      "type": "string"
      +    },
      +    "parentFingerprint": {
      +      "type": "string"
      +    },
      +    "revision": {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "revision",
      +    "parentFingerprint",
      +    "operationId"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "data": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "applied": {
      +          "type": "boolean"
      +        },
      +        "diff": {
      +          "items": {
      +            "additionalProperties": true,
      +            "properties": {
      +              "column": {
      +                "type": "string"
      +              },
      +              "columnLetter": {
      +                "type": "string"
      +              },
      +              "field": {
      +                "type": "string"
      +              },
      +              "from": {},
      +              "to": {}
      +            },
      +            "required": [
      +              "field",
      +              "from",
      +              "to"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "dryRun": {
      +          "type": "boolean"
      +        },
      +        "expenseId": {
      +          "type": "string"
      +        },
      +        "preview": {
      +          "type": "boolean"
      +        },
      +        "reviewExpenseUrl": {
      +          "type": "string"
      +        },
      +        "unmapped": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "applied",
      +        "expenseId",
      +        "diff",
      +        "unmapped"
      +      ],
      +      "type": "object"
      +    },
      +    "finalAnswer": {
      +      "type": "string"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "responseGuidance": {
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "message",
      +    "data"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • 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
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare a mutating, destructive, open-world tool, and the description adds the behavior that matters: a two-phase preview/confirm cycle where omitted confirm writes nothing, a Notes-capacity failure path with a user-facing URL, and the guarantee that fields.paidWith affects only the bookkeeping label with no status or settlement change. The stale-expenseId instruction (search once, never retry the same ID) is operational context the annotations cannot express.

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 is front-loaded in the first clause and every subsequent sentence carries a distinct rule (ID format, two-phase confirm, retry policy, capacity limit, sibling routing) with no filler. It is nonetheless very dense with parentheticals and multiple rules packed together, which slightly raises the risk of a rule being missed on a quick read.

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 four-parameter mutating tool with nested objects, an output schema, and a confirmation flow, the description covers identity requirements, partial-update semantics, the preview/confirm contract, failure modes, and sibling alternatives. Nothing an agent needs to invoke it safely is missing.

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

Parameters5/5

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

Schema coverage is 75%, and the description closes the gaps: expenseId must be the exact full Receipt ID from Column Q and never a date, displayed number, or sheet row number, and expectedPaidWith should be reused from the preview on confirm. It also explains that a blank paidWith clears the override and that omitted fields remain unchanged, adding meaning beyond the schema's own descriptions.

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 ("Update a single existing expense row") and enumerates the editable fields (category, tag, merchant, business purpose) with concrete examples. It also explicitly bounds the tool ("Does not create or delete rows"), so an agent can separate it from correct_expenses and omit_expenses without reading either schema.

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?

Gives explicit routing: same change across multiple rows or attendees goes to correct_expenses, leaving rows out goes to omit_expenses, and amount/date/raw-notes changes require Review Expenses. It also prescribes the confirm workflow and the stale-ID recovery path, 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.