Skip to main content
Glama

Binyan.im · בניינים

Cash box

get_cash_box
Read-only

Cash box balance and movement list for a building: cash payments, cash expenses, cash refunds, explicit deposits and transfers between the cash box and the bank.

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_cash_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds useful scope detail by enumerating which movement categories appear in the list, but says nothing about time ranges, pagination, or whether the balance is point-in-time.

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?

A single compact sentence that front-loads the resource and return shape, then spends its remaining words on the enumerated content. Nothing is redundant, though the colon-separated list is slightly dense.

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 a one-parameter read-only tool with annotations covering the safety profile and no output schema, the description covers purpose and content scope adequately. The main residual gap is the absence of any note on time window or result size.

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?

Only one parameter exists and the schema gives it zero description coverage, so the description must compensate. The phrase 'for a building' does establish that the single parameter scopes the result to one building, but no format or identifier details are added beyond that.

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 names the resource (cash box) and what it returns (balance plus a movement list), then enumerates the movement types covered: cash payments, expenses, refunds, deposits and bank transfers. That is specific enough to distinguish it from a plain payments list, though it never names a sibling it differs from.

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 explicit when-to-use or when-not-to-use guidance. An agent must infer from the content list that this is the tool for cash-box positions rather than, say, get_fund_balance or list_payments; nothing in the text states that choice.

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