Skip to main content
Glama

Binyan.im · בניינים

Update expense

update_expense
DestructiveIdempotent

Update an existing building expense. Only supplied fields change. At least one of amount, description, date, category, vendor, or invoiceNumber is required. Pass null for vendor or invoiceNumber to clear it.

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

Input Schema

NameRequiredDescriptionDefault
dateNo
amountNo
vendorNo
categoryNo
expenseIdYes
buildingIdYes
descriptionNo
cashBoxAmountNo
invoiceNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cashBoxAmount
      Added value: +{
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds real behavior beyond that — partial merge semantics and the null-to-clear convention for vendor/invoiceNumber — but never explains the destructive aspect flagged by the annotations, and the enumerated field list omits cashBoxAmount, leaving it ambiguous whether a cash-box amount change is permitted.

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

Conciseness5/5

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

Three short sentences, front-loaded with the operation, then the merge rule, then the constraint and the clearing convention. No filler and no restatement of the title.

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

Completeness3/5

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

For a destructive mutation with no output schema, the description covers the core merge behavior and the clearing convention, which is the minimum an agent needs. It leaves unresolved whether the updated entity is returned, how cashBoxAmount interacts with the cash box, and what error surfaces when no mutable field is supplied.

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 0%, so the description carries the burden and does document the null-clearing semantics for vendor and invoiceNumber plus the at-least-one rule across six fields. It says nothing about buildingId/expenseId as the identifying pair (uniqueness, error on unknown ID) or about cashBoxAmount, leaving three of nine parameters unaddressed.

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?

The description opens with a specific verb+resource ('Update an existing building expense'), which is clearly distinct from create_expense and the payment/ledger siblings. It stops short of naming an alternative tool or scope boundary, so an agent must infer the create-vs-update split from the names alone.

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

Usage Guidelines3/5

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

It states the partial-update contract ('Only supplied fields change') and the precondition that at least one mutable field be supplied, which is genuine when-to-use guidance. It gives no guidance on choosing between this and create_expense, no prerequisites (permissions, expense state), and no note on whether a failed at-least-one check is an error the caller must pre-empt.

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