Skip to main content
Glama

Binyan.im · בניינים

Fund balance

get_fund_balance
Read-only

כמה כסף יש בקופה. Calculated balance is the opening balance plus payments received minus expenses and bank refunds to residents since the opening balance date. paymentsReceived never counts offsets; offsetCredits reports them separately and refundsPaid is the bank refund total (CASH refunds come out of the cash box instead). Also returns the last bank-synced balance when an imported transaction includes a balance field. The two figures are labeled separately and are not added together.

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

Input Schema

NameRequiredDescriptionDefault
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

With readOnlyHint already declaring the safety profile, the description goes well beyond it: it gives the exact balance formula, states that paymentsReceived excludes offsets, that offsetCredits and refundsPaid are reported separately, and that cash refunds leave the cash box rather than the bank total. It also warns that the bank-synced balance is a second, separate figure that must not be summed — precisely the kind of trap that prevents misexecution. The only shortfall is that it does not describe the shape or labeling of the returned values.

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?

The core formula is stated efficiently and the offset/refund caveats are each load-bearing, but the paragraph is dense and the Hebrew lead sentence adds no machine-usable information for an otherwise English channel and invites confusion with get_cash_box. Content is front-loaded after that opener, so the main loss is clarity, not length.

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?

There is no output schema, so the description carries the burden of explaining returns, and it names the relevant components (paymentsReceived, offsetCredits, refundsPaid, the two balance figures) and their relationship. It stops short of describing the response structure or which fields wrap those values, which is the remaining gap for a read tool with no output schema.

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?

There is a single required parameter, buildingId, with 0% schema description coverage, and the description never mentions it or says whether it must reference an existing building. The baseline for a near-zero-parameter tool is 4, but the lone undocumented parameter pulls this down.

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

Purpose3/5

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

The opening line is Hebrew ("how much money is in the cash box") and the rest explains a computed fund balance, so the resource is identifiable, but the phrasing collides conceptually with the sibling get_cash_box and the description never explicitly says 'this is the calculated fund balance, not the cash-box total.' An agent gets the gist but must read the formula sentence to disambiguate.

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 when-to-use guidance, no mention of when to prefer get_cash_box or get_apartment_ledger instead, and no prerequisites. The only implicit routing signal is the word 'calculated', which the agent must infer.

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