Skip to main content
Glama

add_cash_expense

Add one receiptless expense or client-provided expense advance to the expense sheet after the user confirms; no server preview, it writes on call. Ordinary expenses: list_categories first; use a configured Expense Account. Advances: isClientAdvance=true + clientName reuses/creates the canonical client group, applies Cash advance received and writes a negative expense. Only client money provided before spending; never for vendor refunds, reimbursements, earned fees, retainers or generic deposits. Multiple/incomplete entries, refunds, tax/tip/per diem: Manual expense link from get_spreadsheet_url.

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": {
      "total": "<total>",
      "date": "<date>"
    },
    "name": "add_cash_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxNoTax amount
tipNoTip amount
cityNoCity/location
dateYesExpense date (YYYY-MM-DD)
notesNoNotes or description
totalYesPositive amount paid or received. ExpenseBot stores a client advance as negative.
categoryNoA configured Expense Account returned by list_categories. Do not invent a category.
currencyNoCurrency code (default: USD)
merchantNoMerchant/vendor name for an ordinary expense. Not needed for a client advance; ExpenseBot derives it from clientName.
subtotalNoSubtotal before tax
clientNameNoClient name for a client advance, in ordinary language. ExpenseBot resolves the canonical Client – Name group.
isClientAdvanceNoTrue only when a client supplied money in advance for expenses. Requires clientName and does not require category.

Output Schema

NameRequiredDescriptionDefault
dataNo
expenseNo
messageYes
successYes
recordIdNo
rowNumberNo
finalAnswerNo
spreadsheetUrlNo
responseGuidanceNo
reviewExpensesUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / data / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / expense / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / expense / properties
      Removed value: -{
      -  "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"
      -  }
      -}
    • removedOutput schema / properties / rowNumber / minimum
      Removed value: -1
  2. Changed1 schema field changed
    • 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"
      +}
  3. 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
  4. First observed

TDQS

A4.8/5.0
Behavior5/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 there is no server preview and the write happens on call, that it should run after user confirmation, and the side effects of an advance: it reuses or creates the canonical client group, applies 'Cash advance received', and writes a negative expense. Those are non-obvious mutation consequences an agent would otherwise not know.

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?

The write-on-call constraint and the ordinary-vs-advance split are front-loaded, and every clause carries routing or behavioral information. The telegraphic, semicolon-heavy phrasing ('Advances: isClientAdvance=true + clientName reuses/creates...') is dense and slightly harder to parse than plain sentences, but nothing is padding.

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 mutation tool with an output schema and annotations, the description covers the missing pieces: confirmation timing, absence of preview, the category prerequisite, the advance special case, and where to go for cases it does not handle. Nothing an agent needs to call it correctly is absent.

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 100%, so the baseline is 3, but the description adds cross-parameter meaning: isClientAdvance=true pairs with clientName, replaces the category requirement, and drives merchant derivation, and the amount sign is explained in workflow terms (positive input, negative stored). This largely restates schema text, so it sits just above baseline rather than fully independent.

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 opening sentence states a specific verb and resource ('Add one receiptless expense or client-provided expense advance to the expense sheet') and scopes it to the receiptless/advance case, which separates it from siblings like add_income, add_mileage_entry, and parse_expense. An agent can identify the operation without opening the 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?

It gives explicit branch-by-branch routing: ordinary expenses must call list_categories first and use a configured Expense Account; advances use isClientAdvance=true plus clientName. It also states hard exclusions ('never for vendor refunds, reimbursements, earned fees, retainers or generic deposits') and names the fallback path (Manual expense link from get_spreadsheet_url) for multiple/incomplete entries, refunds, and tax/tip/per diem.

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.