Skip to main content
Glama

Binyan.im · בניינים

Record refund

record_refund

Record money paid back to a resident as a debit on the apartment ledger. The refund first consumes the apartment open credit; any excess becomes an open charge from the refund date. BANK_TRANSFER refunds can be matched to an outgoing bank transaction, while CASH refunds come out of the cash box.

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

Input Schema

NameRequiredDescriptionDefault
dateNo
amountYes
methodNoDefaults to BANK_TRANSFER. CASH refunds come out of the cash box.
buildingIdYes
apartmentIdYes
descriptionNo
referenceNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the ledger mechanics: the refund first consumes apartment open credit and any excess becomes an open charge dated from the refund. It also notes the bank-matching and cash-box implications for the two main methods, though it says nothing about duplicate-submission risk despite idempotentHint=false.

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?

Three tight sentences, front-loaded with the core action and followed by the accounting consequence and the method distinction. The method sentence partly duplicates the schema's own `method` description, a minor redundancy.

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?

A mutation tool with no output schema and only 14% parameter coverage needs the description to explain both effects and inputs; the accounting effect is well covered, but most parameters and the expected result of the call are left undocumented.

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 coverage is only 14%, so the description must carry the load, and it only clarifies `method` semantics (BANK_TRANSFER matchable, CASH from cash box) and hints at `date` via 'from the refund date'. Nothing is said about `referenceNumber`, `description`, or why `buildingId`/`apartmentId` are both required.

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?

States a specific verb and resource ('Record money paid back to a resident') and frames it precisely as a debit on the apartment ledger, which substantively separates it from charge/payment tools. It does not name a sibling alternative explicitly, so it falls short of full differentiation.

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?

The direction of the money (paid back to a resident) implies when this applies versus recording an incoming payment, but no explicit when-to-use, when-not-to-use, or named alternative is given. Guidance is inferred rather than stated.

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