Skip to main content
Glama

Binyan.im · בניינים

Record cash box movement

record_cash_transfer

Record a cash box deposit, a transfer from the cash box to the bank, a withdrawal from the bank to the cash box, or the cash box opening balance. Only the explicit bank transfers can be matched to a bank transaction.

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": "record_cash_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
kindNoDEPOSIT adds cash, TRANSFER_TO_BANK deposits cash into the bank, TRANSFER_FROM_BANK withdraws, OPENING_BALANCE sets the starting balance. Defaults to DEPOSIT.
amountNo
buildingIdYes
descriptionNo
referenceNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent mutation, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: only explicit bank transfers can be matched to a bank transaction, which matters for downstream reconciliation. It does not address duplicate handling despite idempotentHint=false, nor what is returned or whether entries can later be deleted/edited.

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 front-loaded sentence enumerates the valid operations, followed by one short constraint sentence; there is no filler. The enumeration of kinds partially duplicates the schema enum, costing a little space but improving scanability.

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

Completeness2/5

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

This is a 6-parameter mutation tool with no output schema and very low schema description coverage, so the description carries a heavy burden it does not meet. An agent still cannot tell what a successful call returns (an ID? the movement?), how duplicates are treated given idempotentHint=false, or what `referenceNumber` and `date` mean here.

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?

Schema description coverage is only 17% — just the `kind` enum is documented, and its semantics are already fully described in the schema itself, so the description repeats rather than extends. Nothing is said about `amount`, `date`, `buildingId`, `referenceNumber`, or `description`, including that buildingId is the sole required parameter, leaving most parameters undocumented in both places.

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 a specific verb ('Record') and resource ('cash box movement') and then enumerates the four concrete movement kinds (deposit, transfer to bank, withdrawal from bank, opening balance), which makes the tool's scope unambiguous. It does not explicitly distinguish itself from near-neighbors like record_payment or reconcile_transaction, 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 Guidelines3/5

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

Enumerating the four kinds implicitly tells an agent which situations this tool covers, and the closing sentence about bank-transaction matching hints at reconciliation context. However, there is no explicit when-not guidance, no mention of the sibling reconciliation/import tools, and no statement of prerequisites such as needing a building context first.

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