Skip to main content
Glama

Update expense

update_expense
Destructive

Update an expense's details or replace its receipt image.

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": {
      "expense_id": "<expense_id>"
    },
    "name": "update_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoAlias for image_base64.
vendorNo
categoryNo
currencyNo
filenameNo
guide_idNo
spent_onNo
booking_idNo
expense_idYes
activity_idNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
descriptionNo
amount_centsNo
content_typeNo
image_base64NoBase64-encoded receipt image (PNG, JPEG, WebP, GIF, or HEIC).
receipt_data_urlNoA data URL for the receipt image, or null to remove the receipt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description needed to add the dangerous specifics — whether unspecified fields are wiped, whether partial updates are supported, whether receipt removal is possible. 'Replace its receipt image' hints at replacement semantics but leaves the key question (merge vs overwrite) unanswered 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.

Conciseness3/5

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

A single compact sentence with no filler, but it is terse to the point of under-specification rather than being efficiently front-loaded. Nothing is wasted, yet almost nothing is said.

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

Completeness1/5

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

A destructive, 16-parameter mutation with no output schema and sparse schema descriptions requires far more than one sentence. The definition leaves an agent unable to predict merge-vs-replace behavior, alias handling, or receipt deletion side effects.

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

Parameters2/5

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

With 16 parameters and only 25% schema description coverage, the description carries a heavy compensation burden but explains only receipt-image replacement. Aliases (data vs image_base64), the null-to-remove behavior of receipt_data_url, and the roles of booking_id/activity_id/guide_id go entirely unexplained in prose.

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

Purpose4/5

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

Specific verb ('Update') plus resource ('expense') with two named edit modes: scalar fields or receipt image replacement. It does not distinguish itself from siblings like add_expense_receipt or create_expense, and 'details' stays generic across 16 parameters, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over add_expense_receipt for image changes, over create_expense for new records, or over get_expense to inspect first. No preconditions (e.g. that expense_id must exist) are stated.

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.

Resources