Skip to main content
Glama

Binyan.im · בניינים

Record offset

record_offset

Record a resident-paid expense as a dues credit for one apartment (קיזוז). Links the expense and a BUILDING_TAX credit in one step, applies the credit to the oldest unpaid dues and carries any surplus into the next month. No bank transaction is created and the offset is excluded from bank reconciliation. Either pass expenseId to link an existing expense, or amount and description to record a new expense.

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>",
      "apartmentId": "<apartmentId>"
    },
    "name": "record_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate the resident paid the expense. Defaults to the linked expense date.
amountNoCredit amount. Defaults to the linked expense amount.
vendorNo
categoryNoExpense category when creating a new expense. Defaults to Other.
expenseIdNoLink an existing expense instead of creating one.
buildingIdYes
apartmentIdYes
descriptionNoExpense description when creating a new expense, e.g. roof door frame.
cashBoxAmountNoPart of the linked expense that was paid from the building cash box.
invoiceNumberNo
referenceNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

With readOnlyHint=false and destructiveHint=false already supplied, the description still earns credit by disclosing real side effects: the credit is applied to the oldest unpaid dues, surplus rolls into the next month, no bank transaction is created, and the offset is excluded from reconciliation. What it omits is the consequence of idempotentHint=false — whether retrying creates a duplicate credit — and whether a linked expense can be reused across offsets.

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?

Four sentences, front-loaded with the core action, then side effects, then the mode switch. No filler, though the parenthetical '(קיזוז)' and the reconciliation clause could be trimmed for tighter scanning.

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

Completeness4/5

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

For an 11-parameter mutation tool with no output schema, the description covers the two invocation paths, the credit-application order, surplus carry-forward, and the reconciliation exclusion. Missing is any indication of what is returned (the created offset/credit identifiers) and duplicate-submission behavior, which matters given idempotentHint=false.

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 only 55% across 11 parameters, so the description must compensate, and it does for the most consequential ones: it explains that expenseId and amount+description are mutually exclusive modes, and that date/amount default from the linked expense. It adds no meaning for vendor, category, invoiceNumber, referenceNumber, or cashBoxAmount beyond the schema's own text.

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 description gives a specific verb and resource ('Record a resident-paid expense as a dues credit for one apartment') and immediately explains the mechanism: linking an expense with a BUILDING_TAX credit in one step. The clause 'No bank transaction is created and the offset is excluded from bank reconciliation' separates it from sibling write tools like record_payment, which presumably do touch the bank ledger.

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

Usage Guidelines4/5

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

It clearly states the two calling modes ('Either pass expenseId to link an existing expense, or amount and description to record a new expense'), which is the main decision an agent faces. It stops short of naming alternatives such as record_payment or record_refund and saying when those are preferred over an offset.

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